paymentaccuracy.gov
Updated:
2024-05-17 03:23:48 UTC (192 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- paymentaccuracy.gov/A
- paymentaccuracy.gov/AAAA
- paymentaccuracy.gov/NS
- paymentaccuracy.gov/NSEC3PARAM
- paymentaccuracy.gov/SOA
- paymentaccuracy.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 5613)
- gov/DNSKEY (alg 8, id 10104)
- gov/DNSKEY (alg 8, id 64280)
- gov/DS (alg 8, id 64280)
- paymentaccuracy.gov/DNSKEY (alg 13, id 10067)
- paymentaccuracy.gov/DNSKEY (alg 13, id 21076)
- paymentaccuracy.gov/DNSKEY (alg 13, id 34186)
- paymentaccuracy.gov/DS (alg 13, id 21076)
- paymentaccuracy.gov/DS (alg 13, id 34186)
Delegation status
Secure (2)
- . to gov
- gov to paymentaccuracy.gov
Notices
Errors (3)
- paymentaccuracy.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- paymentaccuracy.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- c0vhqksuwx.paymentaccuracy.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- paymentaccuracy.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.49, 198.137.241.113, 198.137.241.177, 2620:10f:b001:6::49, 2620:10f:b001:206::113, 2620:10f:b001:406::177, UDP_-_EDNS0_4096_D_KN)
- paymentaccuracy.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.49, 198.137.241.113, 198.137.241.177, 2620:10f:b001:6::49, 2620:10f:b001:206::113, 2620:10f:b001:406::177, UDP_-_EDNS0_4096_D_KN)
- paymentaccuracy.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.49, 198.137.241.113, 198.137.241.177, 2620:10f:b001:6::49, 2620:10f:b001:206::113, 2620:10f:b001:406::177, UDP_-_EDNS0_4096_D_KN)
- paymentaccuracy.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.49, 198.137.241.113, 198.137.241.177, 2620:10f:b001:6::49, 2620:10f:b001:206::113, 2620:10f:b001:406::177, UDP_-_EDNS0_4096_D_KN)
- paymentaccuracy.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.49, 198.137.241.113, 198.137.241.177, 2620:10f:b001:6::49, 2620:10f:b001:206::113, 2620:10f:b001:406::177, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- paymentaccuracy.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.49, 198.137.241.113, 198.137.241.177, 2620:10f:b001:6::49, 2620:10f:b001:206::113, 2620:10f:b001:406::177, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
