asymco.com

Asymco

Asymco.com created 54 years (19840 days) ago. Asymco.com's 74510 of the World Internet rank of traffic. It has approximately 0.00165% percentage of global internet users and it has approximately 8 169 with 13 888 pageviews. Asymco.com could has about $74 daily from advertising. Search engines provides approximately 7.4% of visits to it. Asymco.com safety for child and for business

Rating asymco.com

8 out of 10 by web.sites

Safety Index

78.75% out of 100%

Popular keywords:: asymco; horace dediu; horace dediu apple; has been actived; asymco horace dediu apple; smartphone penetration per capita hongkong 2010; south korea android users; smartphone penetration per capita hongkong 2013

Reviewed on 2015-06-26 05:42:49

Quick Report for Asymco.com

General information
Ages
Position over in Internet	74510

Estimated data
Pageviews per user	1.7
Daily visitors	8 169
Daily pageviews	13 888
Daily $revenue$	$74
Monthly $revenue$	$2 220

Safe Browsing
Trustwortiness	79%
Realibility	79%
Child Safety	78%
Privacy	79%
Adult	No

Search parameters
Backlinks	158
Indexed pages	5170
Percent visitors from SE	7.4%
Doman search rank	6/10

Hosting information
Hoster	RIPE Network Coordination Centre
Country	Germany
City	Langenbach
IP	83.136.248.81

Owner Information for Asymco.com

No whois info

Hoster & IPs Information of Asymco.com

Detailed information about hoster

Hoster name	RIPE Network Coordination Centre
Hoster country	Germany
Hoster city	Langenbach
Domain IPs	83.136.248.81
DNS information	a.ns.joker.com b.ns.joker.com c.ns.joker.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 159.25.16.137"
#
# Use "?" to get help.
#
#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=159.25.16.137?showDetails=true&showARIN=false&ext=netref2
#
NetRange:       159.25.0.0 - 159.25.255.255
CIDR:           159.25.0.0/16
OriginAS:
NetName:        RIPE-ERX-159-25-0-0
NetHandle:      NET-159-25-0-0-1
Parent:         NET-159-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:        2003-10-29
Updated:        2003-10-29
Ref:            http://whois.arin.net/rest/net/NET-159-25-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 (WHOIS2)

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