commerce.gov

Updated: 2020-07-08 11:26:49 UTC (1599 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 (6)

commerce.gov/A
commerce.gov/AAAA
commerce.gov/MX
commerce.gov/NS
commerce.gov/SOA
commerce.gov/TXT

DNSKEY/DS/NSEC status

Secure (17)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 46594)
./DNSKEY (alg 8, id 48903)
commerce.gov/DNSKEY (alg 8, id 14745)
commerce.gov/DNSKEY (alg 8, id 19987)
commerce.gov/DNSKEY (alg 8, id 2613)
commerce.gov/DNSKEY (alg 8, id 30018)
commerce.gov/DNSKEY (alg 8, id 32535)
commerce.gov/DNSKEY (alg 8, id 59884)
commerce.gov/DS (alg 8, id 19987)
commerce.gov/DS (alg 8, id 19987)
commerce.gov/DS (alg 8, id 59884)
commerce.gov/DS (alg 8, id 59884)
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 commerce.gov

Notices

Errors (16)

commerce.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225)
commerce.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225)
commerce.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:49f0:d064:6:1000::238)
commerce.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:49f0:d064:6:1000::238, UDP_-_NOEDNS_)
commerce.gov/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_NOEDNS_)
commerce.gov/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_NOEDNS_)
commerce.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
commerce.gov/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
commerce.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:49f0:d064:6:1000::238, UDP_-_NOEDNS_)
commerce.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_NOEDNS_)
commerce.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, TCP_-_NOEDNS_)
commerce.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
commerce.gov/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (170.110.225.11, 170.110.225.13, 170.110.225.16, 2610:20:0:20:d0c:90c:225:223, 2610:20:0:20:d0c:90c:225:225, UDP_-_NOEDNS_)
commerce.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
commerce.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
u53wzb8lfk.commerce.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (15)

commerce.gov/DS (alg 8, id 19987): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
commerce.gov/DS (alg 8, id 19987): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
commerce.gov/DS (alg 8, id 19987): 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.
commerce.gov/DS (alg 8, id 19987): 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.
commerce.gov/DS (alg 8, id 59884): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
commerce.gov/DS (alg 8, id 59884): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
commerce.gov/DS (alg 8, id 59884): 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.
commerce.gov/DS (alg 8, id 59884): 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 to commerce.gov: Authoritative AAAA records exist for gpaens2.doc.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
gov to commerce.gov: Authoritative AAAA records exist for hchbens1.doc.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
gov to commerce.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: hchbens2.doc.gov See RFC 1034, Sec. 4.2.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): 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.