frtibtest.gov
Updated:
2021-09-15 18:40:06 UTC (1166 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (4)
- frtibtest.gov/NS
- frtibtest.gov/NSEC3PARAM
- frtibtest.gov/SOA
- frtibtest.gov/TXT
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- frtibtest.gov/DS (alg 7, id 23496)
- frtibtest.gov/DS (alg 8, id 62365)
- gov/DNSKEY (alg 8, id 57735)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Non_existent (5)
- frtibtest.gov/DNSKEY (alg 7, id 23496)
- frtibtest.gov/DNSKEY (alg 7, id 29507)
- frtibtest.gov/DNSKEY (alg 7, id 55874)
- frtibtest.gov/DNSKEY (alg 8, id 19974)
- frtibtest.gov/DNSKEY (alg 8, id 62365)
Delegation status
Bogus (1)
- gov to frtibtest.gov
Secure (1)
- . to gov
Notices
Errors (14)
- frtibtest.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185)
- frtibtest.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.182.186, UDP_-_NOEDNS_)
- frtibtest.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.182.186, UDP_-_EDNS0_512_D_KN)
- frtibtest.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.182.186, UDP_-_NOEDNS_)
- frtibtest.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.182.186, UDP_-_EDNS0_512_D_KN)
- frtibtest.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, UDP_-_NOEDNS_)
- frtibtest.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (149.101.182.186, TCP_-_EDNS0_4096_D_N)
- frtibtest.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.182.186, UDP_-_NOEDNS__0x20)
- gov to frtibtest.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.
- e76d03qrlu.frtibtest.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- frtibtest.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- frtibtest.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- frtibtest.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- frtibtest.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (19)
- RRSIG frtibtest.gov/NS alg 7, id 29507: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG frtibtest.gov/NS alg 7, id 55874: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG frtibtest.gov/NSEC3PARAM alg 7, id 29507: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG frtibtest.gov/NSEC3PARAM alg 7, id 55874: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG frtibtest.gov/SOA alg 7, id 29507: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG frtibtest.gov/SOA alg 7, id 55874: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG frtibtest.gov/TXT alg 7, id 29507: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG frtibtest.gov/TXT alg 7, id 55874: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- frtibtest.gov/DS (alg 7, id 23496): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- frtibtest.gov/DS (alg 7, id 23496): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- frtibtest.gov/DS (alg 7, id 23496): 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.
- frtibtest.gov/DS (alg 7, id 23496): 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.
- frtibtest.gov/DS (alg 8, id 62365): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- frtibtest.gov/DS (alg 8, id 62365): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- frtibtest.gov/DS (alg 8, id 62365): 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.
- frtibtest.gov/DS (alg 8, id 62365): 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.
- frtibtest.gov/NS: 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. (149.101.182.186, UDP_-_EDNS0_4096_D_KN)
- frtibtest.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- frtibtest.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
