HTTP Header reponses of suri-emu.co.jp 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: Thu, 07 Feb 2013 00:56:17 GMT Server: Apache/1.3.42 Ben-SSL/1.60 (Unix) Last-Modified: Thu, 31 Mar 2011 06:55:23 GMT ETag: "bf7cb9-12d1-4d94255b" Accept-Ranges: bytes Content-Length: 4817 Content-Type: text/html
DNS Record Analysis
There are total 7 records in domain name system (DNS) of suri-emu.co.jp, which includes 1 Address(A) record, 2 Mail Exchange(MX) records, 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
suri-emu.co.jp
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.
125.206.128.37
86400
suri-emu.co.jp
MX Mail Exchange Record: Maps a domain name to a list of message transfer agents for that domain.
vcgw1.ocn.ad.jp
86400
pri: 10
suri-emu.co.jp
MX Mail Exchange Record: Maps a domain name to a list of message transfer agents for that domain.
vcgw2.ocn.ad.jp
86400
pri: 10
suri-emu.co.jp
NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers.
ns1.secure.net
86400
suri-emu.co.jp
NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers.
ns2.secure.net
86400
suri-emu.co.jp
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.