optimusalive.com

NOS Alive'15 - 9 • 10 • 11 julho | O Melhor Cartaz. Sempre!

Optimusalive.com created 54 years (19840 days) ago. Optimusalive.com's 883410 of the World Internet rank of traffic. It has approximately 0.00016% percentage of global internet users and it has approximately 814 with 1 709 pageviews. Optimusalive.com could has about $7 daily from advertising. Search engines provides approximately 31.2% of visits to it. Optimusalive.com safety for child.

Rating optimusalive.com

7 out of 10 by web.sites

Safety Index

69.5% out of 100%

Popular keywords:: wow; Optimus; optimus alive; optimus festival; optimus alive 2013; optimus 2013; alive 2013; optimus alive 2013 cartaz; data alive; alive festival 2013

Reviewed on 2015-06-25 13:31:53

Quick Report for Optimusalive.com

General information
Ages
Position over in Internet	883410

Estimated data
Pageviews per user	2.1
Daily visitors	814
Daily pageviews	1 709
Daily $revenue$	$7
Monthly $revenue$	$210

Safe Browsing
Trustwortiness	64%
Realibility	64%
Child Safety	86%
Privacy	64%
Adult	No

Search parameters
Backlinks	92
Indexed pages	22
Percent visitors from SE	31.2%
Doman search rank	6/10

Hosting information
Hoster	RIPE Network Coordination Centre
Country
City
IP	184.168.221.20

Owner Information for Optimusalive.com

No whois info

Hoster & IPs Information of Optimusalive.com

Detailed information about hoster

Hoster name	RIPE Network Coordination Centre
Hoster country
Hoster city
Domain IPs	184.168.221.20
DNS information	ns77.domaincontrol.com ns78.domaincontrol.com

Hoster IPs information

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
#
# Query terms are ambiguous.  The query is assumed to be:
#     "n 130.185.84.30"
#
# Use "?" to get help.
#
#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=130.185.84.30?showDetails=true&showARIN=false&ext=netref2
#
NetRange:       130.185.0.0 - 130.185.255.255
CIDR:           130.185.0.0/16
OriginAS:
NetName:        RIPE-ERX-130-185-0-0
NetHandle:      NET-130-185-0-0-1
Parent:         NET-130-0-0-0-0
NetType:        Early Registrations, Transferred to RIPE NCC
Comment:        These addresses have been further assigned to users in
Comment:        the RIPE NCC region. Contact information can be found in
Comment:        the RIPE database at http://www.ripe.net/whois
RegDate:        2010-11-03
Updated:        2010-11-17
Ref:            http://whois.arin.net/rest/net/NET-130-185-0-0-1
OrgName:        RIPE Network Coordination Centre
OrgId:          RIPE
Address:        P.O. Box 10096
City:           Amsterdam
StateProv:
PostalCode:     1001EB
Country:        NL
RegDate:
Updated:        2011-09-24
Ref:            http://whois.arin.net/rest/org/RIPE
ReferralServer: whois://whois.ripe.net:43
OrgTechHandle: RNO29-ARIN
OrgTechName:   RIPE NCC Operations
OrgTechPhone:  +31 20 535 4444
OrgTechEmail:  ncc@ripe.net
OrgTechRef:    http://whois.arin.net/rest/poc/RNO29-ARIN
OrgAbuseHandle: RNO29-ARIN
OrgAbuseName:   RIPE NCC Operations
OrgAbusePhone:  +31 20 535 4444
OrgAbuseEmail:  ncc@ripe.net
OrgAbuseRef:    http://whois.arin.net/rest/poc/RNO29-ARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
Found a referral to whois.ripe.net:43.
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf
%ERROR:201: access denied for 2a01:4f8:191:20d1:0:0:0:2
%
% Sorry, access from your host has been permanently
% denied because of a repeated excessive querying.
% For more information, see
% http://www.ripe.net/data-tools/db/faq/faq-db/why-did-you-receive-the-error-201-access-denied
% This query was served by the RIPE Database Query Service version 1.66.3 (WHOIS4)

To improve your website's responsiveness, locate your servers close to your main markets. For testing your website speed just put in console ping optimusalive.com. Everything is OK if the average time over 10 pings is less than 300ms.