mastercard.com
Updated:
2023-09-07 17:46:03 UTC (441 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- mastercard.com/A
- mastercard.com/MX
- mastercard.com/NS
- mastercard.com/SOA
- mastercard.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of mastercard.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 4459)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to mastercard.com
Secure (1)
- . to com
Notices
Errors (3)
- mastercard.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2600:1406:32::43)
- mastercard.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2600:1406:32::43, UDP_-_NOEDNS_)
- mastercard.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2600:1406:32::43, UDP_-_NOEDNS_)
Warnings (1)
- com to mastercard.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com zone): dns1.mastercard.com, dns2.mastercard.com See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
