Identity
67
B
bechtel.com
Posture Score: 85/100
Scanned May 24, 2026 at 11:20 AM UTC
Attack Surface
92
Reputation
96
Identity Findings
No NS records found
No nameserver records could be retrieved for this domain.
💡 Ensure NS records are properly configured at your registrar and in your zone file.
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.bechtel.com
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
MTA-STS is in testing mode
The MTA-STS policy is in testing mode and not actively enforcing TLS.
💡 Switch mode to "enforce" once TLS is confirmed working for all MX hosts.
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.
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.
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
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.
TLS-RPT report destinations are reachable
All TLS-RPT rua= URIs point to resolvable domains.
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.
STARTTLS downgrade resistance is adequate
STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.
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=s, aspf=s
DKIM alignment is strict, SPF alignment is strict.
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: pct, rf
The DMARC record contains tags deprecated in DMARCbis: pct, rf. 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.
Open mail ports on mxa-00399f02.gslb.gpphosted.com
Detected open mail-related ports: 25
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2015043758, Refresh: 3600s, Retry: 900s, Expire: 864000s, Min TTL: 86400s
Authorized certificate authorities
CAA records restrict certificate issuance to: digicert.com, globalsign.com
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.
No NSEC/NSEC3 records found
Neither NSEC nor NSEC3 records were found. Authenticated denial of existence is not configured.
💡 Configure NSEC3 records for authenticated denial of existence while preventing zone enumeration.
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.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
5 subdomain(s) discovered for bechtel.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 bechtel.com and its subdomains. Each certificate reveals subdomain names.
Microsoft Autodiscover endpoint detected (authenticated)
The Autodiscover endpoint at autodiscover.bechtel.com is active and requires authentication.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Missing Strict-Transport-Security on bechtel.com
The Strict-Transport-Security header is not set on https://bechtel.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
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://bechtel.com/.well-known/security.txt.
TLS certificate valid for 193 days
Certificate for bechtel.com expires on 2026-12-03.
Certificate issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1
The certificate for bechtel.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for bechtel.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for bechtel.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for bechtel.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on bechtel.com.
No disposable email provider MX records
MX records for bechtel.com do not match known disposable email provider patterns.
No wildcard MX records
No wildcard MX records detected for bechtel.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-00399f02.gslb.gpphosted.com) uses TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (mx0f-00399f02.gpphosted.com) aligns with the MX hostname (mxa-00399f02.gslb.gpphosted.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 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.bechtel.com
HTTPS request to https://webmail.bechtel.com failed or timed out.
WHOIS lookup failed
Could not retrieve WHOIS data for bechtel.com.
Could not determine domain age
WHOIS creation date could not be parsed for bechtel.com.
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: bechel.com (has MX!), bechtle.com (has MX!), vechtel.com (has MX!), hechtel.com (has MX!), echtel.com
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-00399f02.gslb.gpphosted.com
PTR record proves mail server legitimacy
MX: mxa-00399f02.gslb.gpphosted.com
Mail server at 66.159.227.9
→
PTR Record
Reverse DNS: mx0e-00399f02.gpphosted.com
Mail Server Identity: mxb-00399f02.gslb.gpphosted.com
PTR record proves mail server legitimacy
MX: mxb-00399f02.gslb.gpphosted.com
Mail server at 66.159.227.9
→
PTR Record
Reverse DNS: mx0e-00399f02.gpphosted.com
Mail Server Reputation: mxa-00399f02.gslb.gpphosted.com
RBL check ensures server is not blacklisted
MX: mxa-00399f02.gslb.gpphosted.com
Mail server at 66.159.227.9
→
RBL Status
Not blacklisted
Mail Server Reputation: mxb-00399f02.gslb.gpphosted.com
RBL check ensures server is not blacklisted
MX: mxb-00399f02.gslb.gpphosted.com
Mail server at 66.159.227.9
→
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: testing
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 failure reporting configured
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/bechtel.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan bechtel.com Again