time.gov
Updated:
2022-04-25 16:05:47 UTC (942 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- time.gov/A
- time.gov/AAAA
- time.gov/NS
- time.gov/NSEC3PARAM
- time.gov/SOA
- time.gov/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- gov/DNSKEY (alg 8, id 2706)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- time.gov/DNSKEY (alg 8, id 10218)
- time.gov/DNSKEY (alg 8, id 26524)
- time.gov/DS (alg 8, id 26524)
- time.gov/DS (alg 8, id 26524)
Delegation status
Secure (2)
- . to gov
- gov to time.gov
Notices
Errors (14)
- time.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (129.6.13.3, 129.6.13.4, 132.163.4.11, 2610:20:6005:13::3, 2610:20:6005:13::4, 2610:20:6b01:4::11)
- time.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.6.13.4, 2610:20:6b01:4::10, UDP_-_NOEDNS_)
- time.gov/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.6.13.3, UDP_-_NOEDNS_)
- time.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.6.13.3, UDP_-_NOEDNS_)
- time.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (129.6.13.3, 132.163.4.10, UDP_-_EDNS0_512_D_KN)
- time.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.6.13.3, 132.163.4.10, 132.163.4.11, UDP_-_NOEDNS_)
- time.gov/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.6.13.3, UDP_-_NOEDNS_)
- time.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (129.6.13.3, 129.6.13.4, 132.163.4.11, 2610:20:6005:13::3, 2610:20:6005:13::4, 2610:20:6b01:4::11, TCP_-_EDNS0_4096_D_N)
- time.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.6.13.3, 129.6.13.4, 132.163.4.11, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- time.gov/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.6.13.3, UDP_-_NOEDNS_)
- time.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- time.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- 7vsq536l1m.time.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- time.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- gov to time.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): gea3.nist.gov See RFC 1034, Sec. 4.2.2.
- time.gov/DS (alg 8, id 26524): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- time.gov/DS (alg 8, id 26524): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- time.gov/DS (alg 8, id 26524): 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.
- time.gov/DS (alg 8, id 26524): 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.
- time.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- 7vsq536l1m.time.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- time.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
