identitytheft.gov
Updated:
2023-11-11 00:58:53 UTC (376 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- identitytheft.gov/A
- identitytheft.gov/MX
- identitytheft.gov/NS
- identitytheft.gov/SOA
- identitytheft.gov/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- gov/DNSKEY (alg 8, id 10104)
- gov/DNSKEY (alg 8, id 49735)
- gov/DNSKEY (alg 8, id 64280)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 64280)
- gov/DS (alg 8, id 7698)
- identitytheft.gov/DNSKEY (alg 13, id 14432)
- identitytheft.gov/DNSKEY (alg 13, id 46946)
- identitytheft.gov/DNSKEY (alg 13, id 859)
- identitytheft.gov/DS (alg 13, id 14432)
- identitytheft.gov/DS (alg 13, id 14432)
Delegation status
Secure (2)
- . to gov
- gov to identitytheft.gov
Notices
Warnings (4)
- identitytheft.gov/DS (alg 13, id 14432): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- identitytheft.gov/DS (alg 13, id 14432): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- identitytheft.gov/DS (alg 13, id 14432): 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.
- identitytheft.gov/DS (alg 13, id 14432): 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.
