Identity
59
F
nwmutual.com
Posture Score: 48/100
Scanned May 24, 2026 at 11:09 AM UTC
Attack Surface
0
Reputation
85
Identity Findings
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.nwmutual.com
Nameserver unresponsive: ns3.northwesternmutual.com
The nameserver ns3.northwesternmutual.com is not responding on port 53.
💡 Verify that ns3.northwesternmutual.com is properly configured and accessible.
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.nwmutual.com/.well-known/mta-sts.txt
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@nwmutual.com").
ARC check skipped — no MX records
Cannot assess ARC support without MX records.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (154 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.
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.
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
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.
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.
DANE check skipped — no MX records
Cannot check DANE/TLSA without MX records.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open relay check skipped — no MX records
Cannot test for open relay without MX records.
SMTP compliance check skipped — no MX records
Cannot test SMTP compliance without MX records.
Port exposure check skipped — no MX records
Cannot scan ports without MX records.
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
STARTTLS downgrade check skipped — no MX records
Cannot test STARTTLS without MX records.
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
FCrDNS check skipped — no MX records
Cannot perform FCrDNS without MX records.
SOA record parameters
Serial: 5800, Refresh: 10800s, Retry: 3600s, Expire: 2592000s, Min TTL: 900s
Attack Surface Findings
Non-responsive IP for www.nwmutual.com: 164.109.45.92
The subdomain www.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for www.nwmutual.com.
Non-responsive IP for ftp.nwmutual.com: 164.109.45.92
The subdomain ftp.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for ftp.nwmutual.com.
Non-responsive IP for ns1.nwmutual.com: 164.109.45.92
The subdomain ns1.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for ns1.nwmutual.com.
Non-responsive IP for ns2.nwmutual.com: 164.109.45.92
The subdomain ns2.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for ns2.nwmutual.com.
Non-responsive IP for vpn.nwmutual.com: 164.109.45.92
The subdomain vpn.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for vpn.nwmutual.com.
Non-responsive IP for remote.nwmutual.com: 164.109.45.92
The subdomain remote.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for remote.nwmutual.com.
Non-responsive IP for admin.nwmutual.com: 164.109.45.92
The subdomain admin.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for admin.nwmutual.com.
Non-responsive IP for portal.nwmutual.com: 164.109.45.92
The subdomain portal.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for portal.nwmutual.com.
Non-responsive IP for dev.nwmutual.com: 164.109.45.92
The subdomain dev.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for dev.nwmutual.com.
Non-responsive IP for staging.nwmutual.com: 164.109.45.92
The subdomain staging.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for staging.nwmutual.com.
Non-responsive IP for test.nwmutual.com: 164.109.45.92
The subdomain test.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for test.nwmutual.com.
Non-responsive IP for api.nwmutual.com: 164.109.45.92
The subdomain api.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for api.nwmutual.com.
Non-responsive IP for app.nwmutual.com: 164.109.45.92
The subdomain app.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for app.nwmutual.com.
Non-responsive IP for cdn.nwmutual.com: 164.109.45.92
The subdomain cdn.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for cdn.nwmutual.com.
Non-responsive IP for blog.nwmutual.com: 164.109.45.92
The subdomain blog.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for blog.nwmutual.com.
Non-responsive IP for shop.nwmutual.com: 164.109.45.92
The subdomain shop.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for shop.nwmutual.com.
Non-responsive IP for store.nwmutual.com: 164.109.45.92
The subdomain store.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for store.nwmutual.com.
Non-responsive IP for support.nwmutual.com: 164.109.45.92
The subdomain support.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for support.nwmutual.com.
Non-responsive IP for help.nwmutual.com: 164.109.45.92
The subdomain help.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for help.nwmutual.com.
Non-responsive IP for docs.nwmutual.com: 164.109.45.92
The subdomain docs.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for docs.nwmutual.com.
Non-responsive IP for status.nwmutual.com: 164.109.45.92
The subdomain status.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for status.nwmutual.com.
Non-responsive IP for git.nwmutual.com: 164.109.45.92
The subdomain git.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for git.nwmutual.com.
Non-responsive IP for ci.nwmutual.com: 164.109.45.92
The subdomain ci.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for ci.nwmutual.com.
Non-responsive IP for jenkins.nwmutual.com: 164.109.45.92
The subdomain jenkins.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for jenkins.nwmutual.com.
Non-responsive IP for grafana.nwmutual.com: 164.109.45.92
The subdomain grafana.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for grafana.nwmutual.com.
Non-responsive IP for prometheus.nwmutual.com: 164.109.45.92
The subdomain prometheus.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for prometheus.nwmutual.com.
Non-responsive IP for kibana.nwmutual.com: 164.109.45.92
The subdomain kibana.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for kibana.nwmutual.com.
Non-responsive IP for elastic.nwmutual.com: 164.109.45.92
The subdomain elastic.nwmutual.com resolves to 164.109.45.92 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 164.109.45.92 is operational or remove the DNS record for elastic.nwmutual.com.
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.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
Non-mail domain correctly publishes SPF -all
This domain has no MX and publishes "v=spf1 -all", preventing spoofing.
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.
0 subdomain(s) discovered for nwmutual.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 nwmutual.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.nwmutual.com, resolving to 164.109.45.92. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected (authenticated)
The Autodiscover endpoint at autodiscover.nwmutual.com is active and requires authentication.
Reputation Findings
Could not retrieve TLS certificate
Failed to connect to nwmutual.com:443 or retrieve the peer certificate.
💡 Ensure the domain has a valid TLS certificate installed and port 443 is accessible.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
No disposable email provider MX records
MX records for nwmutual.com do not match known disposable email provider patterns.
No wildcard MX records
No wildcard MX records detected for nwmutual.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.
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 nwmutual.com
HTTPS request to https://nwmutual.com failed or timed out.
Could not connect to webmail.nwmutual.com
HTTPS request to https://webmail.nwmutual.com failed or timed out.
WHOIS lookup failed
Could not retrieve WHOIS data for nwmutual.com.
Could not determine domain age
WHOIS creation date could not be parsed for nwmutual.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: nemutual.com (has MX!), namutual.com (has MX!)
2 registered lookalike domain(s) that could be used for phishing against your brand. 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.
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/nwmutual.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan nwmutual.com Again