usa.gov
Updated:
2022-03-28 17:10:08 UTC (973 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- usa.gov/A
- usa.gov/AAAA
- usa.gov/NS
- usa.gov/NSEC3PARAM
- usa.gov/SOA
- usa.gov/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- ./DNSKEY (alg 8, id 9799)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- usa.gov/DNSKEY (alg 8, id 1026)
- usa.gov/DNSKEY (alg 8, id 41371)
- usa.gov/DNSKEY (alg 8, id 7911)
- usa.gov/DS (alg 8, id 4127)
- usa.gov/DS (alg 8, id 41371)
- usa.gov/DS (alg 8, id 41371)
Non_existent (1)
- usa.gov/DNSKEY (alg 8, id 4127)
Delegation status
Secure (2)
- . to gov
- gov to usa.gov
Notices
Errors (5)
- usa.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (159.142.150.68)
- usa.gov/SOA: The TCP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (159.142.150.68, TCP_-_EDNS0_4096_D_N)
- ezkgw6pbdj.usa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- usa.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- usa.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- usa.gov/DS (alg 8, id 41371): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- usa.gov/DS (alg 8, id 41371): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- usa.gov/DS (alg 8, id 41371): 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.
- usa.gov/DS (alg 8, id 41371): 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.
JavaScript is required to make the graph below interactive.
