sovereign.com

Luxury Holidays, Family Holidays, Exclusive Holidays 2015 by Sovereign

Sovereign.com created 54 years (19847 days) ago. Sovereign.com's 251877 of the World Internet rank of traffic. It has approximately 0.00064% percentage of global internet users and it has approximately 3 260 with 9 454 pageviews. Sovereign.com could has about $29 daily from advertising. Search engines provides approximately 22% of visits to it. .

Rating sovereign.com

0 out of 10 by web.sites

Safety Index

0% out of 100%

Popular keywords:: family holiday; honeymoon; honeymoons; Family Holidays; luxury holidays; luxury holiday; Sovereign; jumeirah zabeel saray; Spanish Hotels; sovereign holidays

Reviewed on 2015-06-25 13:59:42

Quick Report for Sovereign.com

General information
Ages
Position over in Internet	251877

Estimated data
Pageviews per user	2.9
Daily visitors	3 260
Daily pageviews	9 454
Daily $revenue$	$29
Monthly $revenue$	$870

Safe Browsing
Trustwortiness	0%
Realibility	0%
Child Safety	0%
Privacy	0%
Adult	No

Search parameters
Backlinks	17
Indexed pages	4540
Percent visitors from SE	22%
Doman search rank	4/10

Hosting information
Hoster	RIPE Network Coordination Centre
Country	United Kingdom
City	Bristol
IP	213.253.11.15

Owner Information for Sovereign.com

No whois info

Hoster & IPs Information of Sovereign.com

Detailed information about hoster

Hoster name	RIPE Network Coordination Centre
Hoster country	United Kingdom
Hoster city	Bristol
Domain IPs	213.253.11.15
DNS information	ns1.netnames.net ns2.netnames.net

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 192.189.157.34"
#
# Use "?" to get help.
#
#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=192.189.157.34?showDetails=true&showARIN=false&ext=netref2
#
NetRange:       192.189.157.0 - 192.189.157.255
CIDR:           192.189.157.0/24
OriginAS:
NetName:        RIPE-ERX-192-189-157-0
NetHandle:      NET-192-189-157-0-1
Parent:         NET-192-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:        2005-02-28
Updated:        2005-02-28
Ref:            http://whois.arin.net/rest/net/NET-192-189-157-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
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
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
#
# 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 (WHOIS1)

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