HTTP Header reponses of gde-my-love.ru 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 gde-my-love.ru, which includes 2 Address(A) 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
gde-my-love.ru
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.
88.198.88.228
3600
gde-my-love.ru
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.
88.198.88.226
3600
gde-my-love.ru
NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers.
ns2.gde-my-love.ru
3600
gde-my-love.ru
NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers.
ns1.gde-my-love.ru
3600
gde-my-love.ru
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.