HTTPS, SSL & Security Report for nokia.com
This report summarizes how well nokia.com is configured for secure web delivery. It covers HTTPS availability, HTTP→HTTPS redirects, TLS/SSL certificate validity, security headers, HTTP/2 and HTTP/3 support, and mixed content. Use it to quickly spot configuration gaps and improve your site's security and trust.
Enabled
Yes
A+ · 1.2, 1.3
4/6
Detailed checks
HTTPS availability
The site is reachable over HTTPS.
Why it matters: HTTPS encrypts traffic and protects user data.
HTTP to HTTPS redirect
Requests to HTTP are redirected to HTTPS.
TLS & CertificateA+
You entered nokia.com. After redirects, browsers use www.nokia.com. Certificate below is for nokia.com. Headers and TLS are from www.nokia.com.
| Valid (nokia.com) | Yes |
| Issuer | C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1 |
| Expires | 2027-01-31 |
| Days until expiry | 131 days |
| OCSP stapling | No |
Certificate for www.nokia.com
| Valid | Yes |
| Subject | C=FI, O=Nokia Solutions and Networks Oy, CN=online.portal.nsn.com |
| Expires | 2026-12-30 (99 days) |
Why it matters: A valid, non-expired certificate ensures encryption is trusted by browsers.
No improvements needed — your configuration meets all requirements for A+.
Monitor this domain
We'll check SSL grade, HTTPS, redirects, and security headers automatically. Email only when something changes.
Free: 1 domain, weekly. Plans from €7/mo — daily checks, up to 50 domains, history & white-label PDF.
Grade breakdownNo improvements needed100/100 pts
No improvements needed — your configuration meets all requirements for A+.
Security headers4/6
- HSTS
- CSP
- X-Frame-Options — sent, but weakSent as "ALLOW-FROM *.nokia.com", which browsers ignore. Use DENY or SAMEORIGIN (or a CSP frame-ancestors directive).
- X-Content-Type-Options
- Referrer-Policy
- Permissions-Policy
Score: 4 of 6 headers effective. For the grade factor (5 pts), 4+ headers and Content-Security-Policy (CSP) are both required. We count a header only when its value actually provides the protection, so a header sent with a weak value counts as “sent, but weak” rather than present. Scanners that count a header as present regardless of its value will report a higher number here.
HSTS (HTTP Strict Transport Security)Enabled
- EnabledYes
- Max-Age365 days
- PreloadNo
Why it matters: HSTS tells browsers to use only HTTPS for this site. Preload allows inclusion in browsers’ built-in HSTS lists.
We check Chromium’s built-in list. hstspreload.org checks eligibility for submission (HSTS header, redirect chain). Results may differ for domains that are preloaded but no longer meet current eligibility rules.
HTTP/2
Negotiated (ALPN h2)
ALPN: h2
HTTP/3 (QUIC)
Advertised + confirmed
Alt-Svc: h3=":443"; ma=93600
Active QUIC negotiation succeeded (curl --http3).
DNS Security
CAA: Not set · DNSSEC: Not signed · HTTPS record: Not setExpand
No HTTPS record. Browsers discover protocols via connection — an HTTPS record speeds this up. Learn more →
No CAA records. Any CA can issue certificates. Consider adding CAA to restrict issuance.
Mixed content
None detected
No HTTP resources were detected on the HTTPS page.
Redirect chain598ms total
When you visit the site over HTTP, the server may send you through one or more redirects until you land on the final HTTPS URL. Shorter chains are faster and better for SEO.
- 1.http://nokia.com295ms
- 2.https://www.nokia.com/303ms
Recommendations for nokia.com
Based on this scan, here are the 3 next steps that would most improve security and SEO for nokia.com.
Add 2 missing security headers
Recommendednokia.com sends 4 of 6 recommended security headers — missing: X-Frame-Options, Permissions-Policy. Most take one line of server config and protect against clickjacking, MIME sniffing and data leaks.
Add a CAA DNS record
Nice to havenokia.com has no CAA record, so any certificate authority can issue certificates for it. A CAA record limits issuance to the CAs you actually use — a cheap defense against mis-issuance.
Enable OCSP stapling
Nice to havenokia.com did not staple an OCSP response on the TLS handshake. Stapling saves a round-trip for visitors and keeps revocation checks off the CA. Informational — it does not affect the SSL grade.
Show this badge on your site
Let your visitors know your SSL setup is verified. The badge always shows your current grade and links to this report. Paste the snippet into your site footer:
← live preview, updates automatically<a href="https://httpsornot.com/report/nokia.com?utm_source=badge" target="_blank" rel="noopener"> <img src="https://httpsornot.com/badge/nokia.com.svg" alt="SSL grade for nokia.com — checked by HTTPS Checker" height="20" loading="lazy" /> </a>
Domain owner? If you want this report removed or made private, contact us.
Need this check in a script or CI? JSON API — free, no key, 120/hour per IP. Shared CI or Google Sheets egress IP? Create a free API key.