patrikhall.com

Updated: 2023-07-22 21:26:57 UTC (488 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 (5)

patrikhall.com/A
patrikhall.com/MX
patrikhall.com/NS
patrikhall.com/SOA
patrikhall.com/TXT

DNSKEY/DS/NSEC status

Secure (14)

./DNSKEY (alg 8, id 11019)
./DNSKEY (alg 8, id 20326)
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 4459)
com/DS (alg 8, id 30909)
patrikhall.com/DNSKEY (alg 14, id 12925)
patrikhall.com/DNSKEY (alg 14, id 13163)
patrikhall.com/DNSKEY (alg 14, id 2236)
patrikhall.com/DNSKEY (alg 14, id 35737)
patrikhall.com/DNSKEY (alg 14, id 49174)
patrikhall.com/DS (alg 14, id 13163)
patrikhall.com/DS (alg 14, id 13163)
patrikhall.com/DS (alg 14, id 2236)
patrikhall.com/DS (alg 14, id 2236)

Delegation status

Secure (2)

. to com
com to patrikhall.com

Notices

Errors (6)

RRSIG patrikhall.com/DNSKEY alg 14, id 12925: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG patrikhall.com/DNSKEY alg 14, id 12925: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG patrikhall.com/DNSKEY alg 14, id 12925: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG patrikhall.com/DNSKEY alg 14, id 12925: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG patrikhall.com/DNSKEY alg 14, id 12925: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
patrikhall.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (10)

com/DS (alg 8, id 30909): 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. (199.7.83.42, UDP_-_EDNS0_4096_D_KN)
com/DS (alg 8, id 30909): 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. (199.7.83.42, UDP_-_EDNS0_4096_D_KN)
patrikhall.com/DS (alg 14, id 13163): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
patrikhall.com/DS (alg 14, id 13163): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
patrikhall.com/DS (alg 14, id 13163): 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.
patrikhall.com/DS (alg 14, id 13163): 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.
patrikhall.com/DS (alg 14, id 2236): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
patrikhall.com/DS (alg 14, id 2236): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
patrikhall.com/DS (alg 14, id 2236): 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.
patrikhall.com/DS (alg 14, id 2236): 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.