shell.com
Updated:
2023-01-24 13:19:43 UTC (668 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- shell.com/A
- shell.com/MX
- shell.com/NS
- shell.com/NSEC3PARAM
- shell.com/SOA
- shell.com/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 36739)
- com/DS (alg 8, id 30909)
- shell.com/DNSKEY (alg 8, id 21682)
- shell.com/DNSKEY (alg 8, id 60561)
- shell.com/DNSKEY (alg 8, id 7740)
- shell.com/DS (alg 8, id 21682)
- shell.com/DS (alg 8, id 21682)
- shell.com/DS (alg 8, id 979)
Non_existent (1)
- shell.com/DNSKEY (alg 8, id 979)
Delegation status
Secure (2)
- . to com
- com to shell.com
Notices
Errors (6)
- shell.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (34.250.153.89, 134.146.80.20)
- shell.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (34.250.153.89, 134.146.80.20, UDP_-_NOEDNS_)
- shell.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (34.250.153.89, 134.146.80.20, UDP_-_NOEDNS_)
- 3krcau765n.shell.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
- shell.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- shell.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
- ./DNSKEY (alg 8, id 20326): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 951): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- com to shell.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: dns4.shell.eu See RFC 1034, Sec. 4.2.2.
- shell.com/DS (alg 8, id 21682): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- shell.com/DS (alg 8, id 21682): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- shell.com/DS (alg 8, id 21682): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- shell.com/DS (alg 8, id 21682): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- shell.com/DS (alg 8, id 979): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- shell.com/DS (alg 8, id 979): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- shell.com/DS (alg 8, id 979): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- shell.com/DS (alg 8, id 979): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- 3krcau765n.shell.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- shell.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- shell.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
