gn
Updated:
2023-10-18 10:08:28 UTC (451 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- gn/NS
- gn/NS
- gn/SOA
- gn/SOA
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- gn/DNSKEY (alg 8, id 21855)
- gn/DNSKEY (alg 8, id 38486)
- gn/DNSKEY (alg 8, id 4180)
- gn/DNSKEY (alg 8, id 9311)
- gn/DS (alg 8, id 38486)
- gn/DS (alg 8, id 9311)
Delegation status
Secure (1)
- . to gn
Notices
Errors (6)
- gn zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (147.28.0.39)
- gn zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (196.216.168.49)
- gn/DNSKEY: No response was received from the server over TCP (tried 2 times). See RFC 1035, Sec. 4.2. (147.28.0.39, TCP_-_EDNS0_4096_D_KN)
- gn/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (196.216.168.49, UDP_-_NOEDNS_)
- gn/SOA: The TCP connection was interrupted (ECONNRESET). See RFC 1035, Sec. 4.2. (147.28.0.39, TCP_-_EDNS0_4096_D_N)
- gn/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
- . to gn: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the . zone): ns1-gn.pch.net See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
