HTTP Header reponses of trafficmotherlode.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 Date: Sat, 10 Jan 2015 23:38:23 GMT Server: Apache Last-Modified: Mon, 22 Dec 2014 17:59:56 GMT Accept-Ranges: bytes Content-Length: 21931 Connection: close Content-Type: text/html
DNS Record Analysis
There are total 6 records in domain name system (DNS) of trafficmotherlode.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
trafficmotherlode.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.
162.144.120.165
14400
trafficmotherlode.com
MX Mail Exchange Record: Maps a domain name to a list of message transfer agents for that domain.
trafficmotherlode.com
14400
pri: 0
trafficmotherlode.com
NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers.
ns2.mowg-crew.com
86400
trafficmotherlode.com
NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers.
ns1.mowg-crew.com
86400
trafficmotherlode.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.