Identity
70
C
deloitte.com
Posture Score: 79/100
Scanned May 24, 2026 at 10:59 AM UTC
Attack Surface
80
Reputation
88
Identity Findings
Weak DKIM RSA key (~1112 bits) for selector 'mandrill'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1112 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
Weak DKIM RSA key (~1296 bits) for selector 'cm'
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.
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.deloitte.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.
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@deloitte.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.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup 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.
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.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
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.
SPF record is 263 bytes (multi-string TXT)
The SPF record exceeds 255 bytes and requires multi-string TXT encoding. Most modern resolvers handle this correctly.
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.
Deprecated DMARCbis tags found: ri
The DMARC record contains tags deprecated in DMARCbis: ri. 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 BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on mx1.hc5291-32.iphmx.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
MX IPs span 2 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2026052046, Refresh: 10800s, Retry: 3600s, Expire: 2419200s, Min TTL: 60s
Attack Surface Findings
Non-routable IPv4 in public DNS: test.deloitte.com → 192.168.0.1
The subdomain test.deloitte.com resolves to non-routable IP 192.168.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
DNS ANY query returns 114 record(s)
The DNS server responds to ANY queries with 114 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
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.
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.
9 subdomain(s) discovered for deloitte.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 deloitte.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain deloitte.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
HSTS effectively disabled on deloitte.com (max-age=0)
The HSTS header has max-age=0, which instructs browsers to forget the HSTS policy. This provides no transport security enforcement.
💡 Set max-age to at least 31536000 (1 year) to enforce HTTPS.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
security.txt present
Found security.txt at https://deloitte.com/.well-known/security.txt.
TLS certificate valid for 121 days
Certificate for deloitte.com expires on 2026-09-22.
Certificate issued by Sectigo Public Server Authentication CA OV R36
The certificate for deloitte.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for deloitte.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for deloitte.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for deloitte.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on deloitte.com.
Domain valid for 331 days
Domain deloitte.com expires on 2027-04-21.
No disposable email provider MX records
MX records for deloitte.com do not match known disposable email provider patterns.
Domain is 11357 days old
Domain deloitte.com was registered 1995-04-20.
No wildcard MX records
No wildcard MX records detected for deloitte.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 (mx1.deloitte.iphmx.com) uses TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (mx1.hc5291-32.iphmx.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.
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 contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
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.deloitte.com
HTTPS request to https://webmail.deloitte.com failed or timed out.
WHOIS registration data
Registrar: Network Solutions, LLC | Created: 1995-04-20 | Expires: 2027-04-21 | Updated: 2026-05-20
WHOIS privacy protection not detected
Domain deloitte.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Typosquat detected: dloitte.com (has MX!), delotite.com (has MX!), depoitte.com (has MX!), delitte.com, deloite.com
7 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 7. 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: mx1.hc5291-32.iphmx.com
PTR record proves mail server legitimacy
MX: mx1.hc5291-32.iphmx.com
Mail server at 216.71.145.13
→
PTR Record
Reverse DNS: 13.145.71.216.in-addr.arpa.iphmx.com
Mail Server Identity: mx1.deloitte.iphmx.com
PTR record proves mail server legitimacy
MX: mx1.deloitte.iphmx.com
Mail server at 68.232.135.188
→
PTR Record
Reverse DNS: 188.135.232.68.in-addr.arpa.iphmx.com
Mail Server Identity: mx2.hc5291-32.iphmx.com
PTR record proves mail server legitimacy
MX: mx2.hc5291-32.iphmx.com
Mail server at 216.71.141.159
→
PTR Record
Reverse DNS: 159.141.71.216.in-addr.arpa.iphmx.com
Mail Server Identity: mx2.deloitte.iphmx.com
PTR record proves mail server legitimacy
MX: mx2.deloitte.iphmx.com
Mail server at 68.232.130.225
→
PTR Record
Reverse DNS: 225.130.232.68.in-addr.arpa.iphmx.com
Mail Server Reputation: mx1.hc5291-32.iphmx.com
RBL check ensures server is not blacklisted
MX: mx1.hc5291-32.iphmx.com
Mail server at 216.71.145.13
→
RBL Status
Not blacklisted
Mail Server Reputation: mx1.deloitte.iphmx.com
RBL check ensures server is not blacklisted
MX: mx1.deloitte.iphmx.com
Mail server at 68.232.135.188
→
RBL Status
Not blacklisted
Mail Server Reputation: mx2.hc5291-32.iphmx.com
RBL check ensures server is not blacklisted
MX: mx2.hc5291-32.iphmx.com
Mail server at 216.71.141.159
→
RBL Status
Not blacklisted
Mail Server Reputation: mx2.deloitte.iphmx.com
RBL check ensures server is not blacklisted
MX: mx2.deloitte.iphmx.com
Mail server at 68.232.130.225
→
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
Mode:
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
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/deloitte.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan deloitte.com Again