Identity
39
C
salesforce.com
Posture Score: 74/100
Scanned May 10, 2026 at 5:08 PM UTC
Score History
Attack Surface
91
Reputation
91
Identity Findings
Weak DKIM RSA key (~1296 bits) for selector 'google'
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.
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.
Weak DKIM RSA key (~1296 bits) for selector 'mandrill'
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.
Inconsistent DNS responses across nameservers
Authoritative nameservers return different answers for the same query.
💡 Verify zone transfers are working correctly and all nameservers serve the same zone data.
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.salesforce.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 does not resolve
The primary nameserver (MNAME) 'mastername.salesforce.com' does not resolve to any IP address.
💡 Ensure the MNAME field points to a resolvable, authoritative nameserver.
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"
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@salesforce.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.
Very low TTL on MX records: 282s
2 MX records have a TTL of 282s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on NS records: 283s
6 NS records have a TTL of 283s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 283s
The DMARC record has a TTL of 283s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (100 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.
MX records are valid
All MX records are properly configured.
2 MX records with 2 unique IPs
Multiple MX records provide mail delivery redundancy.
BIMI record is valid
BIMI is properly configured with a valid logo and DMARC enforcement.
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.
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:d:s
Failure reporting option: 1:d:s
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.
Deprecated DMARCbis tags found: pct
The DMARC record contains tags deprecated in DMARCbis: pct. Consider removing these for forward compatibility.
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.
No VMC authority URL in BIMI record
The BIMI record does not specify a VMC (a= tag). Gmail and Apple Mail require a VMC to display brand logos.
Open mail ports on mxa-00177002.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: 2016673047, Refresh: 600s, Retry: 900s, Expire: 2592000s, Min TTL: 1800s
Attack Surface Findings
Internal information in TXT record
A TXT record for salesforce.com contains references to internal resources: corp.salesforce.com
💡 Remove internal hostnames and IP addresses from public TXT records.
DNS ANY query returns 67 record(s)
The DNS server responds to ANY queries with 67 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
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 email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
17 subdomain(s) discovered for salesforce.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 salesforce.com and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with 0 iteration(s) and salt '7FEA7B83'.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
SMTP banner mismatch: mx0a-00177002.pphosted.com
The SMTP banner identifies as 'mx0a-00177002.pphosted.com' but the MX hostname is 'mxb-00177002.gslb.pphosted.com' and PTR resolves to 'mx0b-00177002.pphosted.com'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (mxb-00177002.gslb.pphosted.com).
HSTS enabled but missing preload directive on salesforce.com
Strict-Transport-Security: max-age=86400
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://salesforce.com/.well-known/security.txt.
TLS certificate valid for 145 days
Certificate for salesforce.com expires on 2026-10-02.
Certificate issued by DigiCert Global G3 TLS ECC SHA384 2020 CA1
The certificate for salesforce.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for salesforce.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for salesforce.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for salesforce.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on salesforce.com.
Domain valid for 163 days
Domain salesforce.com expires on 2026-10-21.
Domain transfer and delete locks enabled
Domain salesforce.com has clientTransferProhibited and clientDeleteProhibited locks.
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 (mxb-00177002.gslb.pphosted.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
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.
Could not connect to webmail.salesforce.com
HTTPS request to https://webmail.salesforce.com failed or timed out.
WHOIS registration data
Registrar: MarkMonitor Inc. | Created: 1998-12-02 | Expires: 2026-10-21 | Updated: 2024-09-19
WHOIS privacy protection not detected
Domain salesforce.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
Typosquat detected: alesforce.com (has MX!), salesorce.com (has MX!), salesfrce.com (has MX!), slaesforce.com (has MX!), salefsorce.com (has MX!)
20 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 20. 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-00177002.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxa-00177002.gslb.pphosted.com
Mail server at 148.163.150.200
→
PTR Record
Reverse DNS: mx0a-00177002.pphosted.com
Mail Server Identity: mxb-00177002.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxb-00177002.gslb.pphosted.com
Mail server at 148.163.154.137
→
PTR Record
Reverse DNS: mx0b-00177002.pphosted.com
Mail Server Reputation: mxa-00177002.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxa-00177002.gslb.pphosted.com
Mail server at 148.163.150.200
→
RBL Status
Not blacklisted
Mail Server Reputation: mxb-00177002.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxb-00177002.gslb.pphosted.com
Mail server at 148.163.154.137
→
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/salesforce.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan salesforce.com Again