shell.com

Updated: 2023-05-02 07:55:13 UTC (570 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

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 (13)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 60955)
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 46551)
com/DS (alg 8, id 30909)
shell.com/DNSKEY (alg 8, id 21682)
shell.com/DNSKEY (alg 8, id 31275)
shell.com/DNSKEY (alg 8, id 44373)
shell.com/DNSKEY (alg 8, id 55983)
shell.com/DNSKEY (alg 8, id 59155)
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, 144.199.196.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, 144.199.196.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, 144.199.196.20, UDP_-_NOEDNS_)
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.
eahozjw0dq.shell.com/A has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (12)

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.
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.
eahozjw0dq.shell.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.