Identity
64
B
mastercard.com
Posture Score: 84/100
Scanned May 10, 2026 at 5:02 PM UTC
Score History
Attack Surface
91
Reputation
96
Identity Findings
Weak DKIM RSA key (~1296 bits) for selector 's2'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
NS delegation mismatch
The registrar-delegated nameservers do not match the zone NS records.
💡 Update either the registrar NS delegation or the zone NS records to match.
No MTA-STS record found
Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.
💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.mastercard.com/.well-known/mta-sts.txt
STARTTLS without MTA-STS or DANE protection
STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.
💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.
SOA MNAME is not authoritative
The primary nameserver (MNAME) 'dns1.mastercard.com' does not return authoritative answers.
💡 Update the MNAME field to point to an authoritative nameserver for this zone.
No CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
Multiple MX records but all resolve to same IP
All MX hostnames resolve to the same IP address, providing no actual redundancy.
💡 Point secondary MX records to a different server IP for true failover.
No TLS-RPT record found
Without TLS-RPT, you will not receive reports about TLS negotiation failures.
💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@mastercard.com").
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
Shared IP 148.163.153.24 used by multiple MX servers
The IP 148.163.153.24 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (192 bytes)
SPF record is within safe DNS packet size limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
All external report destinations authorized
External DMARC report destinations have valid authorization records per RFC 7489 §7.1.
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
MX records are valid
All MX records are properly configured.
BIMI record is valid
BIMI is properly configured with a valid logo and DMARC enforcement.
VMC URL is accessible
The BIMI VMC authority URL is reachable and returns a valid response.
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
IPv6 readiness is good
IPv6 records are present and properly configured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARC failure reporting: fo=1
Failure reports generated when any authentication mechanism fails.
DMARCbis np tag absent
The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
REQUIRETLS not advertised
The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
Open mail ports on mxa-00078002.gslb.pphosted.com
Detected open mail-related ports: 25
RFC 8058 one-click unsubscribe assessment
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2011131623, Refresh: 14400s, Retry: 3600s, Expire: 2419200s, Min TTL: 300s
Attack Surface Findings
Domain enumerability: medium
The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
DNSSEC is not enabled
No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.
💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.
DNS ANY query returns 1 record(s)
The DNS server responds to ANY queries with 1 record(s). The low record count limits amplification risk, but ANY responses still aid reconnaissance.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
9 subdomain(s) discovered for mastercard.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for mastercard.com and its subdomains. Each certificate reveals subdomain names.
1 email SRV record(s) found
Email service SRV records expose mail server configuration for automatic client setup.
Reputation Findings
Missing Strict-Transport-Security on webmail.mastercard.com
The Strict-Transport-Security header is not set on https://webmail.mastercard.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
HSTS enabled with preload on mastercard.com
Strict-Transport-Security: max-age=31536000 ; includeSubDomains ; preload
security.txt present
Found security.txt at https://mastercard.com/.well-known/security.txt.
TLS certificate valid for 165 days
Certificate for mastercard.com expires on 2026-10-22.
Certificate issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1
The certificate for mastercard.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for mastercard.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for mastercard.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for mastercard.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on mastercard.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (mxa-00078002.gslb.pphosted.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (mx0a-00078002.pphosted.com) aligns with the MX hostname (mxa-00078002.gslb.pphosted.com).
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
Abuse contact lookup failed
Could not query abuse contact information.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
WHOIS lookup failed
Could not retrieve WHOIS data for mastercard.com.
Typosquat detected: astercard.com (has MX!), mastecard.com (has MX!), masterard.com (has MX!), mastercar.com (has MX!), mastrecard.com (has MX!)
16 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 16. Domains with MX records can send and receive email, making them high-risk phishing vectors.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record found and configured
→
DMARC Policy
DMARC policy: reject
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature missing
→
DMARC Policy
DMARC policy: reject
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Mail Server Identity: mxa-00078002.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxa-00078002.gslb.pphosted.com
Mail server at 148.163.153.24
→
PTR Record
Reverse DNS: mx0b-00078002.pphosted.com
Mail Server Identity: mxb-00078002.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxb-00078002.gslb.pphosted.com
Mail server at 148.163.153.24
→
PTR Record
Reverse DNS: mx0b-00078002.pphosted.com
Mail Server Reputation: mxa-00078002.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxa-00078002.gslb.pphosted.com
Mail server at 148.163.153.24
→
RBL Status
Not blacklisted
Mail Server Reputation: mxb-00078002.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxb-00078002.gslb.pphosted.com
Mail server at 148.163.153.24
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
MTA-STS not configured
⚠️ MTA-STS policy is missing. Even with TLS support, you lack the enforcement layer that prevents attackers from stripping encryption (downgrade attacks).
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: reject
→
BIMI Record
Brand logo configured
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✗
DMARC Policy
✓
BIMI Record
✓
CAA Records
✗
DNSSEC
✗
MTA-STS
✗
TLS-RPT
✗
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/mastercard.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan mastercard.com Again