ofia.gov
Updated:
2022-05-20 13:34:41 UTC (918 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (4)
- ofia.gov/NS
- ofia.gov/NSEC3PARAM
- ofia.gov/SOA
- ofia.gov/TXT
DNSKEY/DS/NSEC status
Bogus (3)
- ofia.gov/DNSKEY (alg 8, id 10474)
- ofia.gov/DNSKEY (alg 8, id 28086)
- ofia.gov/DNSKEY (alg 8, id 63678)
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- gov/DNSKEY (alg 8, id 2706)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- ofia.gov/DS (alg 8, id 41419)
- ofia.gov/DS (alg 8, id 5932)
Non_existent (2)
- ofia.gov/DNSKEY (alg 8, id 41419)
- ofia.gov/DNSKEY (alg 8, id 5932)
Delegation status
Bogus (1)
- gov to ofia.gov
Secure (1)
- . to gov
Notices
Errors (7)
- gov to ofia.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. (2.22.230.67, 95.100.173.65, 95.101.36.64, 96.7.50.66, 184.85.248.66, 193.108.91.55, 2600:1401:2::37, 2600:1480:800::43, 2a02:26f0:117::42, UDP_-_EDNS0_4096_D_KN)
- gov to ofia.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (2.22.230.67, 95.100.173.65, 95.101.36.64, 96.7.50.66, 184.85.248.66, 193.108.91.55, 2600:1401:2::37, 2600:1480:800::43, 2a02:26f0:117::42, UDP_-_EDNS0_4096_D_KN)
- ofia.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- ofia.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ofia.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- cid1uqprlj.ofia.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ofia.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
- ofia.gov/DS (alg 8, id 41419): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ofia.gov/DS (alg 8, id 41419): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ofia.gov/DS (alg 8, id 41419): 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.
- ofia.gov/DS (alg 8, id 41419): 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.
- ofia.gov/DS (alg 8, id 5932): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ofia.gov/DS (alg 8, id 5932): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ofia.gov/DS (alg 8, id 5932): 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.
- ofia.gov/DS (alg 8, id 5932): 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.
- ofia.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- ofia.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- ofia.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- cid1uqprlj.ofia.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- ofia.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
