ssa.gov
Updated:
2023-01-18 21:02:20 UTC (674 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- ssa.gov/A
- ssa.gov/AAAA
- ssa.gov/MX
- ssa.gov/NS
- ssa.gov/NSEC3PARAM
- ssa.gov/SOA
- ssa.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- gov/DNSKEY (alg 8, id 24250)
- gov/DNSKEY (alg 8, id 56278)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- ssa.gov/DNSKEY (alg 13, id 24110)
- ssa.gov/DNSKEY (alg 13, id 36417)
- ssa.gov/DS (alg 13, id 36417)
- ssa.gov/DS (alg 13, id 36417)
Delegation status
Secure (2)
- . to gov
- gov to ssa.gov
Notices
Errors (2)
- t5a1hjkuxz.ssa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ssa.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- ssa.gov/DS (alg 13, id 36417): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ssa.gov/DS (alg 13, id 36417): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ssa.gov/DS (alg 13, id 36417): 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.
- ssa.gov/DS (alg 13, id 36417): 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.
- t5a1hjkuxz.ssa.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- ssa.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
