mastercard.com
Updated:
2022-08-05 17:07:44 UTC (842 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 20326)
- ./DNSKEY (alg 8, id 20826)
- NSEC3 proving non-existence of mastercard.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 32298)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to mastercard.com
Secure (1)
- . to com
Notices
Warnings (4)
- com to mastercard.com: Authoritative AAAA records exist for dns1.mastercard.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to mastercard.com: Authoritative AAAA records exist for dns2.mastercard.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com/DS (alg 8, id 30909): 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)
- com/DS (alg 8, id 30909): 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.
