earmarks.gov
Updated:
2024-04-20 05:25:07 UTC (216 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- earmarks.gov/A
- earmarks.gov/AAAA
- earmarks.gov/NS
- earmarks.gov/NSEC3PARAM
- earmarks.gov/SOA
- earmarks.gov/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 5613)
- earmarks.gov/DNSKEY (alg 13, id 62448)
- earmarks.gov/DNSKEY (alg 13, id 9666)
- earmarks.gov/DS (alg 13, id 35847)
- earmarks.gov/DS (alg 13, id 9666)
- gov/DNSKEY (alg 8, id 10104)
- gov/DNSKEY (alg 8, id 64280)
- gov/DS (alg 8, id 64280)
Non_existent (1)
- earmarks.gov/DNSKEY (alg 13, id 35847)
Delegation status
Secure (2)
- . to gov
- gov to earmarks.gov
Notices
Errors (8)
- earmarks.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (198.137.240.49, 198.137.241.49, 2620:10f:b000:6::49, 2620:10f:b001:6::49)
- earmarks.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:10f:b000:6::49, 2620:10f:b001:6::49, UDP_-_NOEDNS_)
- earmarks.gov/A: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (198.137.240.49, 198.137.241.49, UDP_-_EDNS0_4096_D_KN)
- earmarks.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:10f:b000:6::49, 2620:10f:b001:6::49, UDP_-_NOEDNS_)
- earmarks.gov/NS: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (198.137.240.49, 198.137.241.49, UDP_-_EDNS0_4096_D_KN)
- earmarks.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- p6yj5bud0n.earmarks.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- earmarks.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- earmarks.gov/A: 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. (198.137.241.113, 198.137.241.177, 2620:10f:b001:206::113, 2620:10f:b001:406::177, UDP_-_EDNS0_4096_D_KN)
- earmarks.gov/AAAA: 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. (198.137.241.113, 198.137.241.177, 2620:10f:b001:206::113, 2620:10f:b001:406::177, UDP_-_EDNS0_4096_D_KN)
- earmarks.gov/NS: 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. (198.137.241.113, 198.137.241.177, 2620:10f:b001:206::113, 2620:10f:b001:406::177, UDP_-_EDNS0_4096_D_KN)
- earmarks.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. (198.137.241.113, 198.137.241.177, 2620:10f:b001:206::113, 2620:10f:b001:406::177, UDP_-_EDNS0_4096_D_KN)
- earmarks.gov/SOA: 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. (198.137.241.113, 198.137.241.177, 2620:10f:b001:206::113, 2620:10f:b001:406::177, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- earmarks.gov/TXT: 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. (198.137.241.113, 198.137.241.177, 2620:10f:b001:206::113, 2620:10f:b001:406::177, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
