frtibtest.gov

Updated: 2022-01-19 19:37:47 UTC (1039 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Bogus (5)

frtibtest.gov/MX
frtibtest.gov/NS
frtibtest.gov/NSEC3PARAM
frtibtest.gov/SOA
frtibtest.gov/TXT

DNSKEY/DS/NSEC status

Bogus (4)

frtibtest.gov/DNSKEY (alg 7, id 32238)
frtibtest.gov/DNSKEY (alg 7, id 33944)
frtibtest.gov/DNSKEY (alg 8, id 57955)
frtibtest.gov/DNSKEY (alg 8, id 58224)

Secure (8)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 9799)
frtibtest.gov/DS (alg 7, id 23496)
frtibtest.gov/DS (alg 8, id 62365)
gov/DNSKEY (alg 8, id 6229)
gov/DNSKEY (alg 8, id 7030)
gov/DNSKEY (alg 8, id 7698)
gov/DS (alg 8, id 7698)

Non_existent (2)

frtibtest.gov/DNSKEY (alg 7, id 23496)
frtibtest.gov/DNSKEY (alg 8, id 62365)

Delegation status

Bogus (1)

gov to frtibtest.gov

Secure (1)

. to gov

Notices

Errors (18)

frtibtest.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (149.101.82.186, 149.101.182.185)
frtibtest.gov zone: There was an error resolving the following NS name(s) to address(es): ns-va01.frtibtest.gov, ns-va02.frtibtest.gov
frtibtest.gov/DNSKEY: 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/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.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.82.185, 149.101.82.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.82.186, UDP_-_EDNS0_512_D_KN)
frtibtest.gov/NSEC3PARAM: 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.82.185, 149.101.82.186, 149.101.182.185, 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.82.185, UDP_-_NOEDNS_)
frtibtest.gov/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.186, UDP_-_NOEDNS_)
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. (149.101.182.186, UDP_-_EDNS0_4096_D_KN)
gov to frtibtest.gov: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (149.101.182.186, UDP_-_EDNS0_4096_D_KN)
gov to frtibtest.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. (149.101.182.186, UDP_-_EDNS0_4096_D_KN)
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.
2mcjead9sk.frtibtest.gov/A 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 (32)

RRSIG frtibtest.gov/DNSKEY alg 7, id 32238: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG frtibtest.gov/DNSKEY alg 7, id 32238: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG frtibtest.gov/DNSKEY alg 7, id 32238: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG frtibtest.gov/DNSKEY alg 7, id 32238: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG frtibtest.gov/DNSKEY alg 7, id 33944: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG frtibtest.gov/DNSKEY alg 7, id 33944: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG frtibtest.gov/DNSKEY alg 7, id 33944: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG frtibtest.gov/DNSKEY alg 7, id 33944: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG frtibtest.gov/MX alg 7, id 33944: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG frtibtest.gov/MX alg 7, id 33944: 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 33944: 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 33944: 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 33944: 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 33944: 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 33944: 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 33944: 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 33944: 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 33944: 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 33944: 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/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. (149.101.182.186, UDP_-_EDNS0_4096_D_KN)
frtibtest.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
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.
frtibtest.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.