naver.com
HTTPS & TLS
81/100B- Certificate expiry173/4
The certificate expires in 17 days.
- TLS versionTLS 1.22/4
Negotiates TLS 1.2 at best; TLS 1.3 is faster and drops old ciphers.
- Old protocolsTLS 1.10/3
Still accepts TLS 1.1, retired by browsers in 2020 and open to downgrade attacks.
- HTTPS certificateDigiCert Inc10/10
HTTPS with a valid certificate from DigiCert Inc.
- Key strengthRSA 20482/2
A strong key: RSA 2048.
- HTTP → HTTPS3013/3
http:// redirects straight to https://.
- HSTS2 years4/4
HSTS tells browsers to use HTTPS only, for 2 years.
- HTTP/2 and HTTP/3HTTP/22/2
HTTP/2.
DNS
64/100D- DNSSEC0/3
Not signed with DNSSEC: a forged DNS answer for the domain cannot be told from the real one.
- CAA records0/2
No CAA records: any certificate authority may issue certificates for the domain.
- Name servers34/4
3 name servers for the domain.
- Name servers answer3/35/5
Every name server answers for the domain, with the same version of the zone.
- DMARCnone2/7
DMARC only watches (p=none): mail that fakes the domain is still delivered.
- MTA-STS0/2
No MTA-STS: mail to the domain can be read in transit by stripping its encryption.
- TLS reporting0/0.5
No TLS reporting: failed encrypted deliveries go unnoticed.
- DKIM
No DKIM key at the common selectors; it may use one that cannot be guessed.
- SPF~all4/5
SPF lists the servers allowed to send its mail and marks the rest as suspicious (~all).
Web & network
38/100F- Content Security Policy0/3
No Content Security Policy: an injected script runs with the page's full rights.
- X-Content-Type-Options0/2
No X-Content-Type-Options: browsers may run an upload as a script.
- Referrer-Policyunsafe-url0/0.5
No Referrer-Policy of its own (browsers' default applies).
- Permissions-Policy0/0.5
No Permissions-Policy: embedded content may ask for camera, microphone or location.
- IPv60/4
www.naver.com has no IPv6 address: IPv6-only networks reach it only through translation.
- Framing2/2
Other sites cannot frame its pages (clickjacking protection).
- RPKIvalid4/4
The route to the website is RPKI-valid: networks can reject hijacked announcements of it.
Dependencies
80/100B- DNS providersSelf-hosted3/5
All DNS is with one provider (Self-hosted): an outage there takes the domain offline, as Dyn's did in 2016.
- One company for everything5/5
The website, DNS and email do not all hang on one company.
Who runs it
- Website
- Akamai
- DNS
- Self-hosted
- Self-hosted
Routes
- 23.12.156.0/22AS16625RPKI valid
Name servers
- ns1.naver.comSelf-hostedAS23576
- ns2.naver.comSelf-hostedAS23576
- ns3.naver.comSelf-hostedAS23576
README badge
Show the grade in your README or docs; it updates when the domain is graded again.
[](https://skycisa.com/grade/naver.com)Compare with…
What is graded
A valid certificate (an invalid one means F), its expiry against its lifetime, TLS 1.3, no TLS 1.0/1.1 (else at most B), http:// sent straight to https://, HSTS, HTTP/2.
At least two name servers that all answer and agree, DNSSEC, CAA records, and a registration that is not about to expire.
SPF, a DMARC policy that rejects forgeries (none means at most B), MTA-STS and TLS reporting for domains that take mail, DKIM at common selectors.
Content Security Policy, nosniff, framing protection, Referrer- and Permissions-Policy, IPv6, and an RPKI-valid route (invalid means at most C).
DNS from more than one provider, and the website, DNS and email not all with one company.
A+ 95–100 · A 85–94 · B 75–84 · C 65–74 · D 50–64 · F below 50