pay.gov
Updated:
2023-04-22 22:48:09 UTC (581 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- pay.gov/AAAA
- pay.gov/NS
- pay.gov/SOA
- pay.gov/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- gov/DNSKEY (alg 8, id 50011)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- pay.gov/DNSKEY (alg 13, id 38600)
- pay.gov/DNSKEY (alg 13, id 54752)
- pay.gov/DS (alg 13, id 54752)
Delegation status
Secure (2)
- . to gov
- gov to pay.gov
Notices
Errors (5)
- pay.gov/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (156.154.64.108, 156.154.65.108, 156.154.66.108, 156.154.67.108, 2001:502:4612::90, 2001:502:f3ff::90, 2610:a1:1014::90, 2610:a1:1015::90, UDP_-_NOEDNS_)
- pay.gov/AAAA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2610:a1:1015::90, UDP_-_NOEDNS_)
- pay.gov/AAAA: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (2610:a1:1015::90, UDP_-_EDNS0_4096_D_KN)
- pay.gov/AAAA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2610:a1:1015::90, UDP_-_EDNS0_4096_D_KN)
- pay.gov/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (156.154.64.108, 156.154.65.108, 156.154.67.108, 2001:502:4612::90, 2001:502:f3ff::90, 2610:a1:1014::90, UDP_-_NOEDNS_)
JavaScript is required to make the graph below interactive.
