safecom.gov
Updated:
2020-04-17 18:48:30 UTC (1679 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (4)
- safecom.gov/A
- safecom.gov/MX
- safecom.gov/NS
- safecom.gov/SOA
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- gov/DNSKEY (alg 8, id 36558)
- gov/DNSKEY (alg 8, id 40176)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- safecom.gov/DS (alg 13, id 2371)
Non_existent (1)
- safecom.gov/DNSKEY (alg 13, id 2371)
Delegation status
Bogus (1)
- gov to safecom.gov
Secure (1)
- . to gov
Notices
Errors (11)
- gov to safecom.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (205.251.192.5, 205.251.195.89, 205.251.196.78, 205.251.199.127, 2600:9000:5300:500::1, 2600:9000:5303:5900::1, 2600:9000:5304:4e00::1, 2600:9000:5307:7f00::1, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- gov to safecom.gov: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no DS RR matched a DNSKEY with algorithm 13 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (205.251.192.5, 205.251.195.89, 205.251.196.78, 205.251.199.127, 2600:9000:5300:500::1, 2600:9000:5303:5900::1, 2600:9000:5304:4e00::1, 2600:9000:5307:7f00::1, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- safecom.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.192.5, 205.251.195.89, 205.251.196.78, 205.251.199.127, 2600:9000:5300:500::1, 2600:9000:5303:5900::1, 2600:9000:5304:4e00::1, 2600:9000:5307:7f00::1, UDP_-_EDNS0_4096_D_K)
- safecom.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.192.5, 205.251.195.89, 205.251.196.78, 205.251.199.127, 2600:9000:5300:500::1, 2600:9000:5303:5900::1, 2600:9000:5304:4e00::1, 2600:9000:5307:7f00::1, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- safecom.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.192.5, 205.251.195.89, 205.251.196.78, 205.251.199.127, 2600:9000:5300:500::1, 2600:9000:5303:5900::1, 2600:9000:5304:4e00::1, 2600:9000:5307:7f00::1, UDP_-_EDNS0_4096_D_K)
- safecom.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.192.5, 205.251.195.89, 205.251.196.78, 205.251.199.127, 2600:9000:5300:500::1, 2600:9000:5303:5900::1, 2600:9000:5304:4e00::1, 2600:9000:5307:7f00::1, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- safecom.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- safecom.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- ulfkyh9s2m.safecom.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- safecom.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- safecom.gov/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov/DS (alg 8, id 7698): 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.
- gov/DS (alg 8, id 7698): 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.
