Identity
47
B
mail.ractermx.com
Posture Score: 81/100
Scanned May 10, 2026 at 5:14 AM UTC
Score History
Attack Surface
95
Reputation
100
Identity Findings
No SPF record found
The domain has no SPF record, allowing anyone to send email as this domain.
💡 Publish an SPF TXT record (e.g. "v=spf1 include:_spf.google.com -all").
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.mail.ractermx.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@mail.ractermx.com").
No MX records found
The domain has no MX records and cannot receive email.
💡 Publish MX records pointing to your mail server(s).
No DKIM records found
No DKIM records were found for any common selector. Email may not be authenticated.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.mail.ractermx.com
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
Attack Surface Findings
Non-mail domain has no SPF record
This domain has no MX records (does not receive mail) but also has no SPF record. Without "v=spf1 -all", attackers can spoof this domain in phishing emails.
💡 Publish "v=spf1 -all" to explicitly declare this domain sends no mail.
No MX records — A-record fallback active
The domain has no MX records but has an A record. Per RFC 5321, mail servers will attempt delivery to the A record IP. This domain may be silently accepting mail without SPF/DKIM/DMARC protection.
💡 If this domain should not receive mail, publish a Null MX record (RFC 7505): "0 ." as the MX. If it should receive mail, add proper MX records.
Reputation Findings
HSTS enabled with preload on mail.ractermx.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://mail.ractermx.com/.well-known/security.txt.
TLS certificate valid for 63 days
Certificate for mail.ractermx.com expires on 2026-07-13.
Certificate issued by E8
The certificate for mail.ractermx.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for mail.ractermx.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for mail.ractermx.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for mail.ractermx.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on mail.ractermx.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
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.
No abuse contacts resolved
Could not resolve abuse contact information for MX IPs via abusix.org.
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.mail.ractermx.com
HTTPS request to https://webmail.mail.ractermx.com failed or timed out.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record missing
→
DMARC Policy
DMARC policy missing
⚠️ SPF record is missing. DMARC relies on SPF to verify sender authorization. Without SPF, DMARC alignment will fail, reducing email deliverability and brand protection.
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 missing
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC not enforced (p=none or missing)
→
BIMI Record
BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
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/mail.ractermx.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan mail.ractermx.com Again