gsaig.gov
Updated:
2022-08-11 08:25:23 UTC (835 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- gsaig.gov/A
- gsaig.gov/MX
- gsaig.gov/NS
- gsaig.gov/NSEC3PARAM
- gsaig.gov/SOA
- gsaig.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- gov/DNSKEY (alg 8, id 261)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gsaig.gov/DNSKEY (alg 8, id 1365)
- gsaig.gov/DNSKEY (alg 8, id 31459)
- gsaig.gov/DNSKEY (alg 8, id 636)
- gsaig.gov/DS (alg 8, id 31459)
- gsaig.gov/DS (alg 8, id 31459)
Delegation status
Secure (2)
- . to gov
- gov to gsaig.gov
Notices
Errors (3)
- gsaig.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- gsaig.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- 5xwry3h9cm.gsaig.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- gsaig.gov/DS (alg 8, id 31459): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gsaig.gov/DS (alg 8, id 31459): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gsaig.gov/DS (alg 8, id 31459): 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.
- gsaig.gov/DS (alg 8, id 31459): 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.
