jpmorganchase.com
Updated:
2022-05-17 21:09:10 UTC (922 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- jpmorganchase.com/A
- jpmorganchase.com/NS
- jpmorganchase.com/SOA
- jpmorganchase.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- NSEC3 proving non-existence of jpmorganchase.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 37269)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to jpmorganchase.com
Secure (1)
- . to com
Notices
Warnings (2)
- ./DNSKEY (alg 8, id 20326): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 47671): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
