Identity
80
A
scan.ractermx.com
Posture Score: 93/100
Scanned May 9, 2026 at 4:41 AM UTC
Score History
Attack Surface
100
Reputation
100
Identity Findings
MX hostname does not resolve:
The MX hostname has no A or AAAA records.
💡 Ensure the MX hostname resolves to a valid IP address.
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.scan.ractermx.com
No DMARC aggregate report URI (rua=)
Without rua=, you will not receive aggregate reports about authentication results.
💡 Add rua=mailto:dmarc-reports@scan.ractermx.com to your DMARC record.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (11 bytes)
SPF record is within safe DNS packet size limits.
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
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.
DMARC alignment: adkim=s, aspf=s
DKIM alignment is strict, SPF alignment is strict.
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.
Attack Surface Findings
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.
Null MX properly configured
The domain publishes a Null MX record (RFC 7505), explicitly declaring it does not accept mail.
Reputation Findings
HSTS enabled with preload on scan.ractermx.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://scan.ractermx.com/.well-known/security.txt.
TLS certificate valid for 64 days
Certificate for scan.ractermx.com expires on 2026-07-13.
Certificate issued by E8
The certificate for scan.ractermx.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for scan.ractermx.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for scan.ractermx.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for scan.ractermx.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on scan.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.
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.scan.ractermx.com
HTTPS request to https://webmail.scan.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 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:
PTR record proves mail server legitimacy
MX:
Mail server at
→
PTR Record
No PTR record
⚠️ Mail server () lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation:
RBL check ensures server is not blacklisted
MX:
Mail server at
→
RBL Status
Not blacklisted
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 policy: reject
→
BIMI Record
BIMI not configured
⚠️ BIMI record is missing. Even with DMARC enforcement, you need to configure BIMI to display your brand logo in supported email clients.
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/scan.ractermx.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan scan.ractermx.com Again