everytrycounts.gov

Updated: 2020-04-13 17:43:47 UTC (1683 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 (4)

everytrycounts.gov/A
everytrycounts.gov/NS
everytrycounts.gov/SOA
everytrycounts.gov/TXT

DNSKEY/DS/NSEC status

Secure (14)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 48903)
everytrycounts.gov/DNSKEY (alg 7, id 27255)
everytrycounts.gov/DNSKEY (alg 7, id 30119)
everytrycounts.gov/DNSKEY (alg 7, id 48711)
everytrycounts.gov/DS (alg 7, id 27255)
everytrycounts.gov/DS (alg 7, id 27255)
everytrycounts.gov/DS (alg 7, id 48711)
everytrycounts.gov/DS (alg 7, id 48711)
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)

Delegation status

Secure (2)

. to gov
gov to everytrycounts.gov

Notices

Errors (7)

everytrycounts.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:f220:418:4101::80e7:401)
everytrycounts.gov/A: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D)
everytrycounts.gov/NS: No response was received from the server over UDP (tried 14 times). See RFC 1035, Sec. 4.2. (2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_)
everytrycounts.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
everytrycounts.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
ixt2bdwfgl.everytrycounts.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
everytrycounts.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (33)

RRSIG everytrycounts.gov/A alg 7, id 30119: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG everytrycounts.gov/DNSKEY alg 7, id 27255: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG everytrycounts.gov/DNSKEY alg 7, id 27255: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG everytrycounts.gov/DNSKEY alg 7, id 27255: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG everytrycounts.gov/DNSKEY alg 7, id 30119: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG everytrycounts.gov/DNSKEY alg 7, id 30119: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG everytrycounts.gov/DNSKEY alg 7, id 30119: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG everytrycounts.gov/DNSKEY alg 7, id 48711: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG everytrycounts.gov/DNSKEY alg 7, id 48711: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG everytrycounts.gov/DNSKEY alg 7, id 48711: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG everytrycounts.gov/NS alg 7, id 30119: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG everytrycounts.gov/SOA alg 7, id 30119: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG everytrycounts.gov/TXT alg 7, id 30119: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
everytrycounts.gov/DNSKEY (alg 7, id 27255): 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_K)
everytrycounts.gov/DNSKEY (alg 7, id 30119): 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_K)
everytrycounts.gov/DNSKEY (alg 7, id 48711): 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_K)
everytrycounts.gov/DS (alg 7, id 27255): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
everytrycounts.gov/DS (alg 7, id 27255): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
everytrycounts.gov/DS (alg 7, id 27255): 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.
everytrycounts.gov/DS (alg 7, id 27255): 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.
everytrycounts.gov/DS (alg 7, id 48711): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
everytrycounts.gov/DS (alg 7, id 48711): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
everytrycounts.gov/DS (alg 7, id 48711): 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.
everytrycounts.gov/DS (alg 7, id 48711): 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): 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.
everytrycounts.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
everytrycounts.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
everytrycounts.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
ixt2bdwfgl.everytrycounts.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
everytrycounts.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.