HTTP Header reponses of essonne-location.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 500 Internal Server Error Date: Mon, 18 Mar 2013 12:42:50 GMT Server: Apache Set-Cookie: 99e345487ff2bbae1273f64acfa034df=804hr3860hll1t91i0cs3kab26; path=/ X-Powered-By: PleskLin Connection: close Transfer-Encoding: chunked Content-Type: text/html
DNS Record Analysis
There are total 6 records in domain name system (DNS) of essonne-location.com, which includes 1 Address(A) record, 1 Mail Exchange(MX) record, 2 Name Server(NS) records, 1 Start of Authority(SOA) record and 1 Text(TXT) record.
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
essonne-location.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.
5.39.70.64
86399
essonne-location.com
MX Mail Exchange Record: Maps a domain name to a list of message transfer agents for that domain.
mail.essonne-location.com
86400
pri: 10
essonne-location.com
NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers.
ns2270950.ovh.net
86399
essonne-location.com
NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers.
sdns2.ovh.net
86399
essonne-location.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.
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.