Identity
27
C
nginx.com
Posture Score: 73/100
Scanned May 10, 2026 at 6:01 AM UTC
Score History
Attack Surface
92
Reputation
99
Identity Findings
Overly broad CIDR range: 149.72.0.0/16
The /16 CIDR block authorizes a very large IP range to send email as this domain.
💡 Narrow the IP range to only the specific servers that send email.
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.nginx.com
External report destination not authorized: f5.com
The ruf= URI sends reports to f5.com, but no authorization record exists at nginx.com._report._dmarc.f5.com. Reports will be silently dropped by compliant receivers.
💡 Ask the owner of f5.com to publish a TXT record at nginx.com._report._dmarc.f5.com containing 'v=DMARC1'.
Subdomains have no DMARC enforcement
No sp= tag set and p=none. Subdomains inherit the monitoring-only policy, leaving them open to spoofing.
💡 Add sp=reject (or sp=quarantine) to your DMARC record to protect subdomains.
DMARC policy is monitoring-only (p=none)
The p=none policy only monitors; it does not instruct receivers to quarantine or reject unauthenticated mail.
💡 Upgrade to p=quarantine or p=reject after reviewing aggregate reports.
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.nginx.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.
Generic ISP PTR hostname: esa.hc5801-97.iphmx.com
The PTR record for 68.232.154.38 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.nginx.com
Generic ISP PTR hostname: esa.hc5801-97.iphmx.com
The PTR record for 139.138.58.65 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.nginx.com
Generic ISP PTR hostname: esa.hc5801-97.iphmx.com
The PTR record for 68.232.154.38 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.nginx.com
Generic ISP PTR hostname: esa.hc5801-97.iphmx.com
The PTR record for 139.138.58.65 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.nginx.com
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"
Void lookup: include:spf1.mailgun.org
The mechanism include:spf1.mailgun.org returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
Void lookup: include:spf2.mailgun.org
The mechanism include:spf2.mailgun.org returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
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@nginx.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.
Shared IP 68.232.154.38 used by multiple MX servers
The IP 68.232.154.38 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 139.138.58.65 used by multiple MX servers
The IP 139.138.58.65 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Very low TTL on TXT records: 276s
10 TXT records have a TTL of 276s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 276s
The SPF record has a TTL of 276s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
NS TTL mismatch between parent and authoritative zone
The NS record TTL in the parent zone (~7176s) differs significantly from the authoritative zone (~86400s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
MX records are valid
All MX records are properly configured.
2 MX records with 2 unique IPs
Multiple MX records provide mail delivery redundancy.
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.
SPF record is 439 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.hc5801-97.iphmx.com
Detected open mail-related ports: 25
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
MX IPs span 2 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2025051975, Refresh: 28800s, Retry: 7200s, Expire: 604800s, Min TTL: 86400s
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.
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 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.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
7 subdomain(s) discovered for nginx.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 nginx.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
HSTS enabled but missing preload directive on nginx.com
Strict-Transport-Security: max-age=31536000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://nginx.com/.well-known/security.txt.
TLS certificate valid for 81 days
Certificate for nginx.com expires on 2026-07-30.
Certificate issued by E7
The certificate for nginx.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for nginx.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for nginx.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for nginx.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on nginx.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.hc5801-97.iphmx.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (esa.hc5801-97.iphmx.com) aligns with the MX hostname (mx1.hc5801-97.iphmx.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 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.nginx.com
HTTPS request to https://webmail.nginx.com failed or timed out.
WHOIS lookup failed
Could not retrieve WHOIS data for nginx.com.
Typosquat detected: ginx.com (has MX!), ngnx.com (has MX!), ngin.com (has MX!), nignx.com (has MX!), ngnix.com (has MX!)
16 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 16. 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 missing
→
DMARC Policy
DMARC policy: none
⚠️ 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: none
⚠️ 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.hc5801-97.iphmx.com
PTR record proves mail server legitimacy
MX: mx1.hc5801-97.iphmx.com
Mail server at 68.232.154.38
→
PTR Record
Reverse DNS: esa.hc5801-97.iphmx.com
Mail Server Identity: mx2.hc5801-97.iphmx.com
PTR record proves mail server legitimacy
MX: mx2.hc5801-97.iphmx.com
Mail server at 68.232.154.38
→
PTR Record
Reverse DNS: esa.hc5801-97.iphmx.com
Mail Server Reputation: mx1.hc5801-97.iphmx.com
RBL check ensures server is not blacklisted
MX: mx1.hc5801-97.iphmx.com
Mail server at 68.232.154.38
→
RBL Status
Not blacklisted
Mail Server Reputation: mx2.hc5801-97.iphmx.com
RBL check ensures server is not blacklisted
MX: mx2.hc5801-97.iphmx.com
Mail server at 68.232.154.38
→
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 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
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/nginx.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan nginx.com Again