max.gov
Updated:
2023-04-11 17:20:34 UTC (592 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- max.gov/A
- max.gov/AAAA
- max.gov/MX
- max.gov/NS
- max.gov/NSEC3PARAM
- max.gov/SOA
- max.gov/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- ./DNSKEY (alg 8, id 951)
- gov/DNSKEY (alg 8, id 24250)
- gov/DNSKEY (alg 8, id 50011)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- max.gov/DNSKEY (alg 13, id 19611)
- max.gov/DNSKEY (alg 13, id 24547)
- max.gov/DNSKEY (alg 13, id 51559)
- max.gov/DS (alg 13, id 19611)
- max.gov/DS (alg 13, id 19611)
Delegation status
Secure (2)
- . to gov
- gov to max.gov
Notices
Errors (3)
- gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (209.112.123.30)
- 7iwzexmy0j.max.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- max.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- max.gov/DS (alg 13, id 19611): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- max.gov/DS (alg 13, id 19611): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- max.gov/DS (alg 13, id 19611): 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.
- max.gov/DS (alg 13, id 19611): 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.
- 7iwzexmy0j.max.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- max.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
