paymentaccuracy.gov
Updated:
2025-06-23 20:28:17 UTC (14 days ago)
Update now
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 (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 38696)
- ./DNSKEY (alg 8, id 46441)
- ./DNSKEY (alg 8, id 53148)
- gov/DNSKEY (alg 13, id 2536)
- gov/DNSKEY (alg 13, id 35496)
- gov/DS (alg 13, id 2536)
- paymentaccuracy.gov/DNSKEY (alg 13, id 2346)
- paymentaccuracy.gov/DNSKEY (alg 13, id 4786)
- paymentaccuracy.gov/DNSKEY (alg 13, id 60813)
- paymentaccuracy.gov/DS (alg 13, id 2346)
- paymentaccuracy.gov/DS (alg 13, id 60813)
Delegation status
Secure (2)
- . to gov
- gov to paymentaccuracy.gov
Notices
Errors (5)
- qd594.1uwvr.paymentaccuracy.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- paymentaccuracy.gov/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- 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.
- paymentaccuracy.gov/CDS 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. (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. (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. (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. (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. (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. (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.
