Destinationluxury.com Website Stats

destinationluxury.com
(Updated 3531 days ago)
Domain : destinationluxury.com
Domain Title : Destination Luxury - Luxury Living Redefined
WRPageWRPage : Complete In-Page SEO Analysis New Feature
WRScore WRScore(beta) is calculated on the basis of pageviews, unique visitors and unique content. :
destinationluxury.com Reviewed by WebRankStats on Sep 16 . Rating: Rating: 2.34 out of 10
Website IP : 184.168.47.225
Hosting Country : UNITED STATES

General Information

Meta Description :
Meta Keywords :
XML Sitemap :
Robots.txt :
Gzip Compress :
Text/HTML Ratio : 5.32%

Website Ranks

Alexa Rank : 282,604 visit Alexa
Compete Rank : N/A visit Compete
Quantcast Rank : N/A visit Quantcast

Website Safety

McAfee SiteAdvisor : green visit SiteAdvisor
WOT : Mostly visit WOT

Pages Indexed

Google : 1,710 visit Google
Bing : 5 visit Bing

Sociometer

Facebook Likes : 1,320
Stumbleupon : 19
LinkedIn : 51

Server Analysis

IP Address : 184.168.47.225
Latitude : 33.602
Longitude : -111.888
Region : SCOTTSDALE, ARIZONA
Country : UNITED STATES

HTTP Header Analysis

HTTP Header reponses of destinationluxury.com is the information we get when HTTP request sent to a server from connecting clients(e.g. chrome, firefox). When you input an address into your browser it sends a request to the server hosting the domain and the server responds. HTTP Header information is not directly displayed by normal web browsers like chrome, firefox etc.

HTTP/1.1 200 OK
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
X-Pingback: http://destinationluxury.com/xmlrpc.php
Set-Cookie: PHPSESSID=4qonkc1hod8u8n1muuvph5ptt5; path=/
Content-Type: text/html; charset=UTF-8
X-Port: port_10421
X-Cacheable: NO:Not Cacheable
Date: Tue, 16 Sep 2014 17:46:26 GMT
Age: 0
Connection: close
Vary: Accept-Encoding, User-Agent
X-Cache: uncached
X-Backend: wpaas_web_003

DNS Record Analysis

There are total 9 records in domain name system (DNS) of destinationluxury.com, which includes 1 Address(A) record, 2 Mail Exchange(MX) records, 2 Name Server(NS) records, 1 Start of Authority(SOA) record and 3 Text(TXT) records.

Host Name of the node to which this record pertains Type Type of resource record in symbolic representation. IP/Target TTL Count of seconds that the resource record stays valid. Extra Info Additional resource record-specific data
destinationluxury.com A Address Record: A 32-bit IPv4 address, most commonly used to map hostnames to an IP address of the host, but also used for DNSBLs, storing subnet masks in RFC 1101. 184.168.47.225 600
destinationluxury.com MX Mail Exchange Record: Maps a domain name to a list of message transfer agents for that domain. smtp.secureserver.net 3600 pri: 0
destinationluxury.com MX Mail Exchange Record: Maps a domain name to a list of message transfer agents for that domain. mailstore1.secureserver.net 3600 pri: 10
destinationluxury.com NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers. ns25.domaincontrol.com 3600
destinationluxury.com NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers. ns26.domaincontrol.com 3600
destinationluxury.com SOA Start of Authority Record: Specifies authoritative information about a DNS zone, including the primary name server, the email of the domain administrator, the domain serial number, and several timers relating to refreshing the zone. 3600 mname: ns25.domaincontrol.com
rname: dns.jomax.net
serial: 2014071600
refresh: 28800
retry: 7200
expire: 604800
minimum-ttl: 3600
destinationluxury.com TXT Text Record: Originally for arbitrary human-readable text in a DNS record. Since the early 1990s, however, this record more often carries machine-readable data, such as specified by RFC 1464, opportunistic encryption, Sender Policy Framework, DKIM, DMARC DNS-SD. 3600 txt: google-site-verification=zX-DP9xQLcU3EzxN725TRqHi4pPlAS2YLm6Pu0r6py8
entries: Array
destinationluxury.com TXT Text Record: Originally for arbitrary human-readable text in a DNS record. Since the early 1990s, however, this record more often carries machine-readable data, such as specified by RFC 1464, opportunistic encryption, Sender Policy Framework, DKIM, DMARC DNS-SD. 3600 txt: google-site-verification=oSRnoMtiFAcBOONAQ022Aa2kEG-BwbaEjgMgPmy1vUw
entries: Array
destinationluxury.com TXT Text Record: Originally for arbitrary human-readable text in a DNS record. Since the early 1990s, however, this record more often carries machine-readable data, such as specified by RFC 1464, opportunistic encryption, Sender Policy Framework, DKIM, DMARC DNS-SD. 3600 txt: google-site-verification=MWGMeTLQwcTnuIX8JN8HiNsKoaIb9A9fVl_1_uQFLhk
entries: Array

Traffic Graphs

Alexa Graph