glb.cdc.gov

Updated: 2021-04-20 11:34:45 UTC (1315 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

Secure (2)

glb.cdc.gov/NS
glb.cdc.gov/SOA

DNSKEY/DS/NSEC status

Secure (14)

./DNSKEY (alg 8, id 14631)
./DNSKEY (alg 8, id 20326)
cdc.gov/DNSKEY (alg 7, id 42473)
cdc.gov/DNSKEY (alg 7, id 65139)
cdc.gov/DS (alg 7, id 65139)
cdc.gov/DS (alg 7, id 65139)
glb.cdc.gov/DNSKEY (alg 7, id 11349)
glb.cdc.gov/DNSKEY (alg 7, id 19472)
glb.cdc.gov/DS (alg 7, id 11349)
glb.cdc.gov/DS (alg 7, id 23883)
gov/DNSKEY (alg 8, id 27306)
gov/DNSKEY (alg 8, id 48498)
gov/DNSKEY (alg 8, id 7698)
gov/DS (alg 8, id 7698)

Non_existent (1)

glb.cdc.gov/DNSKEY (alg 7, id 23883)

Delegation status

Secure (3)

. to gov
cdc.gov to glb.cdc.gov
gov to cdc.gov

Notices

Errors (10)

cdc.gov to glb.cdc.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. (198.246.110.76, 198.246.125.102, UDP_-_EDNS0_4096_D_KN)
cdc.gov to glb.cdc.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. (198.246.110.76, 198.246.125.102, UDP_-_EDNS0_4096_D_KN)
glb.cdc.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (198.246.110.76, 198.246.125.102)
glb.cdc.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (198.246.110.76, 198.246.125.102, TCP_-_EDNS0_4096_D_N)
glb.cdc.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
glb.cdc.gov/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
85z4aebtp3.glb.cdc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
glb.cdc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
glb.cdc.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
glb.cdc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (33)

RRSIG cdc.gov/DNSKEY alg 7, id 42473: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG cdc.gov/DNSKEY alg 7, id 42473: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG cdc.gov/DNSKEY alg 7, id 65139: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG cdc.gov/DNSKEY alg 7, id 65139: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG glb.cdc.gov/DNSKEY alg 7, id 11349: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG glb.cdc.gov/DNSKEY alg 7, id 11349: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG glb.cdc.gov/DNSKEY alg 7, id 19472: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG glb.cdc.gov/DNSKEY alg 7, id 19472: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG glb.cdc.gov/DS alg 7, id 42473: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG glb.cdc.gov/DS alg 7, id 42473: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG glb.cdc.gov/NS alg 7, id 19472: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG glb.cdc.gov/NS alg 7, id 19472: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG glb.cdc.gov/SOA alg 7, id 19472: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG glb.cdc.gov/SOA alg 7, id 19472: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG glb.cdc.gov/SOA alg 7, id 19472: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
cdc.gov/DS (alg 7, id 65139): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
cdc.gov/DS (alg 7, id 65139): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
cdc.gov/DS (alg 7, id 65139): 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.
cdc.gov/DS (alg 7, id 65139): 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.
glb.cdc.gov/DS (alg 7, id 11349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
glb.cdc.gov/DS (alg 7, id 11349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
glb.cdc.gov/DS (alg 7, id 23883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
glb.cdc.gov/DS (alg 7, id 23883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
gov to cdc.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): icdc-us-ns1.cdc.gov, icdc-us-ns3.cdc.gov, icdc-us-ns2.cdc.gov See RFC 1034, Sec. 4.2.2.
gov to cdc.gov: The following NS name(s) were found in the delegation NS RRset (i.e., in the gov zone), but not in the authoritative NS RRset: auth00.ns.uu.net, auth100.ns.uu.net See RFC 1034, Sec. 4.2.2.
glb.cdc.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
glb.cdc.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
glb.cdc.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
85z4aebtp3.glb.cdc.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
glb.cdc.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
glb.cdc.gov/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
glb.cdc.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
glb.cdc.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.