naver.com

Name: naver.com Email Security Posture Assessment
Creator: RacterMX
License: https://creativecommons.org/licenses/by-nc/4.0/

Posture Score: 45/100

Scanned May 27, 2026 at 7:01 PM UTC

Identity

Attack Surface

Reputation

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.

critical

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.

high

Cannot check DNS consistency — no NS records

No nameserver records could be retrieved for consistency checking.

💡 Ensure NS records are properly configured.

high

No DKIM records found

No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.

💡 Configure DKIM signing and publish the public key at <selector>._domainkey.naver.com

medium

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.

medium

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.naver.com/.well-known/mta-sts.txt

medium

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.

medium

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"

medium

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@naver.com").

low

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.

low

SPF record is valid

The SPF record is properly configured with valid syntax and within lookup limits.

pass

SPF record length OK (174 bytes)

SPF record is within safe DNS packet size limits.

pass

DKIM cryptographic configuration is compliant

No RFC 8301 compliance issues detected in DKIM key configuration.

pass

All external report destinations authorized

External DMARC report destinations have valid authorization records per RFC 7489 §7.1.

pass

No deprecated DMARCbis tags present

The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).

pass

MX records are valid

All MX records are properly configured.

pass

Meets bulk sender authentication requirements

Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.

pass

SMTP security checks passed

No open relay, VRFY/EXPN, or banner disclosure issues detected.

pass

SMTP RFC 5321 compliance checks passed

The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.

pass

DNS TTL values follow best practices

All critical DNS record TTLs are within recommended ranges.

pass

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.

informational

DMARC alignment: adkim=r, aspf=r

DKIM alignment is relaxed, SPF alignment is relaxed.

informational

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.

informational

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.

informational

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.

informational

No DANE/TLSA records found

DANE is not configured for any MX server. This is optional but provides strong certificate binding.

informational

No BIMI record found

BIMI is not configured. Your brand logo will not display in supporting email clients.

informational

Open mail ports on mx5.mail.naver.com

Detected open mail-related ports: 25

informational

Domain is IPv4-only

No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.

informational

RFC 8058 one-click unsubscribe assessment

No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.

informational

MX IP network diversity

MX IPs span 2 different /16 networks, providing good diversity.

informational

SOA record parameters

Serial: 2026052701, Refresh: 21600s, Retry: 1800s, Expire: 1209600s, Min TTL: 180s

informational

Attack Surface Findings

DNS ANY query returns 21 record(s)

The DNS server responds to ANY queries with 21 record(s), creating significant DNS amplification risk.

💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.

medium

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.

medium

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.

medium

All MX records resolve correctly

No dangling MX records detected — all MX hostnames resolve to valid IP addresses.

pass

Explicit MX records present

The domain has explicit MX records — no implicit A-record fallback delivery.

pass

No internal information leakage detected

No non-routable IP addresses or internal references were found in public DNS records.

pass

No email autodiscovery endpoints detected

No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.

pass

19 subdomain(s) discovered for naver.com

Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.

informational

0 certificate(s) found in CT logs

Certificate Transparency logs contain 0 certificate(s) for naver.com and its subdomains. Each certificate reveals subdomain names.

informational

Reputation Findings

Listed on korea.services.net

202.131.26.30 (mx5.mail.naver.com) is listed on blacklist korea.services.net (response: 127.0.0.2).

💡 Visit the korea.services.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.

critical

Listed on dnsbl.spfbl.net

125.209.222.14 (mx3.naver.com) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.3).

💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.

critical

Listed on korea.services.net

125.209.222.14 (mx3.naver.com) is listed on blacklist korea.services.net (response: 127.0.0.2).

💡 Visit the korea.services.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.

critical

Listed on korea.services.net

125.209.238.100 (mx1.naver.com) is listed on blacklist korea.services.net (response: 127.0.0.2).

💡 Visit the korea.services.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.

critical

Listed on dnsbl.spfbl.net

125.209.238.137 (mx2.naver.com) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.3).

💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.

critical

Listed on korea.services.net

125.209.238.137 (mx2.naver.com) is listed on blacklist korea.services.net (response: 127.0.0.2).

💡 Visit the korea.services.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.

critical

Listed on korea.services.net

202.131.24.28 (mx4.mail.naver.com) is listed on blacklist korea.services.net (response: 127.0.0.2).

💡 Visit the korea.services.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.

critical

Listed on korea.services.net

202.131.24.29 (mx6.mail.naver.com) is listed on blacklist korea.services.net (response: 127.0.0.2).

💡 Visit the korea.services.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.

critical

HSTS enabled but missing preload directive on naver.com

Strict-Transport-Security: max-age=63072000; includeSubdomains

💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.

low

security.txt present

Found security.txt at https://naver.com/.well-known/security.txt.

pass

TLS certificate valid for 38 days

Certificate for naver.com expires on 2026-07-05.

pass

Certificate issued by E7

The certificate for naver.com is issued by a third-party CA.

pass

Signature algorithm: ecdsa-with-sha384

The certificate for naver.com uses an acceptable signature algorithm.

pass

ECC key: 256 bits

The certificate for naver.com uses an adequate ECC key of 256 bits.

pass

SCTs present in certificate

The certificate for naver.com contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on naver.com.

pass

No disposable email provider MX records

MX records for naver.com do not match known disposable email provider patterns.

pass

No wildcard MX records

No wildcard MX records detected for naver.com.

pass

TLD has good reputation

The .com TLD is not on known abuse watchlists.

pass

DMARC reporting destinations look legitimate

DMARC rua/ruf addresses do not point to known URL shortener services.

pass

MX records point to stable infrastructure

No MX records point to known dynamic DNS service domains.

pass

Strong TLS configuration on primary MX

Primary MX (mx1.naver.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.

pass

SMTP banner matches infrastructure identity

The SMTP banner (mx.naver.com) aligns with the MX hostname (mx3.naver.com).

pass

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.

informational

Abuse contacts found for MX IPs

Abuse contact information retrieved via abusix.org DNS lookup.

informational

PhishTank — API key required

PhishTank phishing database check requires an API key.

informational

Sender Score — API key required

Sender Score reputation check requires an API key.

informational

Cisco Talos — API key required

Cisco Talos IP reputation check requires an API key.

informational

Could not connect to webmail.naver.com

HTTPS request to https://webmail.naver.com failed or timed out.

informational

WHOIS lookup failed

Could not retrieve WHOIS data for naver.com.

informational

Could not determine domain age

WHOIS creation date could not be parsed for naver.com.

informational

Bulletproof Hosting Detection — API key required

Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.

informational

Threat Intelligence Feeds — API key required

Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).

informational

Typosquat detected: aver.com (has MX!), nave.com (has MX!), anver.com (has MX!), navre.com (has MX!), baver.com (has MX!)

24 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 24. Domains with MX records can send and receive email, making them high-risk phishing vectors.

informational

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: none

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: mx5.mail.naver.com

PTR record proves mail server legitimacy

MX: mx5.mail.naver.com Mail server at 202.131.26.30 → PTR Record Reverse DNS: mx5.naver.com

Mail Server Identity: mx3.naver.com

PTR record proves mail server legitimacy

MX: mx3.naver.com Mail server at 125.209.222.14 → PTR Record Reverse DNS: mx3.naver.com

Mail Server Identity: mx1.naver.com

PTR record proves mail server legitimacy

MX: mx1.naver.com Mail server at 125.209.238.100 → PTR Record Reverse DNS: mx1.naver.com

Mail Server Identity: mx2.naver.com

PTR record proves mail server legitimacy

MX: mx2.naver.com Mail server at 125.209.238.137 → PTR Record Reverse DNS: mx2.naver.com

Mail Server Identity: mx4.mail.naver.com

PTR record proves mail server legitimacy

MX: mx4.mail.naver.com Mail server at 202.131.24.28 → PTR Record Reverse DNS: mx4.naver.com

Mail Server Identity: mx6.mail.naver.com

PTR record proves mail server legitimacy

MX: mx6.mail.naver.com Mail server at 202.131.24.29 → PTR Record Reverse DNS: mx6.naver.com

Mail Server Reputation: mx5.mail.naver.com