secretservice.gov
Updated:
2022-11-25 14:20:18 UTC (728 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (8)
- secretservice.gov/A
- secretservice.gov/AAAA
- secretservice.gov/AAAA
- secretservice.gov/MX
- secretservice.gov/NS
- secretservice.gov/NSEC3PARAM
- secretservice.gov/SOA
- secretservice.gov/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 56278)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- secretservice.gov/DNSKEY (alg 8, id 11540)
- secretservice.gov/DNSKEY (alg 8, id 22234)
- secretservice.gov/DNSKEY (alg 8, id 59526)
- secretservice.gov/DNSKEY (alg 8, id 6201)
- secretservice.gov/DS (alg 8, id 11540)
- secretservice.gov/DS (alg 8, id 11540)
- secretservice.gov/DS (alg 8, id 22234)
Delegation status
Secure (2)
- . to gov
- gov to secretservice.gov
Notices
Errors (3)
- secretservice.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (23.211.61.66, UDP_-_EDNS0_512_D_KN)
- 5bqr06gi9o.secretservice.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- secretservice.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
- secretservice.gov/DS (alg 8, id 11540): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- secretservice.gov/DS (alg 8, id 11540): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- secretservice.gov/DS (alg 8, id 11540): 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.
- secretservice.gov/DS (alg 8, id 11540): 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.
- secretservice.gov/NSEC3PARAM: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (23.211.61.66, UDP_-_EDNS0_4096_D_KN)
- secretservice.gov/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (23.211.61.66, UDP_-_EDNS0_4096_D_KN)
- secretservice.gov/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (23.211.61.66, UDP_-_EDNS0_4096_D_KN_0x20)
- 5bqr06gi9o.secretservice.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- secretservice.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
