HTTP Header reponses of opusdata.in 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.
There are total 6 records in domain name system (DNS) of opusdata.in, 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
opusdata.in
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.
66.96.131.28
3600
opusdata.in
MX Mail Exchange Record: Maps a domain name to a list of message transfer agents for that domain.
mx.opusdata.in
3600
pri: 30
opusdata.in
NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers.
ns1.ipower.com
3600
opusdata.in
NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers.
ns2.ipower.com
3600
opusdata.in
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.
WebRankStats
Meta Description : 
visit SiteAdvisor
visit WOT
