_domainkey.paypal.com
Updated:
2020-07-16 14:35:12 UTC (5 years ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (2)
- _domainkey.paypal.com/TXT (NODATA)
- paypal.com/SOA
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- NSEC proving non-existence of _domainkey.paypal.com/TXT
- com/DNSKEY (alg 8, id 24966)
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 39844)
- com/DS (alg 8, id 30909)
- paypal.com/DNSKEY (alg 5, id 11811)
- paypal.com/DNSKEY (alg 5, id 21037)
- paypal.com/DS (alg 5, id 21037)
Delegation status
Secure (2)
- . to com
- com to paypal.com
Notices
Warnings (7)
- RRSIG NSEC proving non-existence of _domainkey.paypal.com/TXT alg 5, id 11811: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG paypal.com/DNSKEY alg 5, id 11811: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG paypal.com/DNSKEY alg 5, id 11811: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG paypal.com/DNSKEY alg 5, id 21037: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG paypal.com/DNSKEY alg 5, id 21037: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG paypal.com/SOA alg 5, id 11811: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- paypal.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
