HTTPS, SSL & Security Report for captn.cc

This report summarizes how well captn.cc 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.

SecureScore90/100Last checked: 24 Jun 2026 at 16:16 UTC
HTTPS

Enabled

HTTP → HTTPS

Yes

TLS

A · 1.2, 1.3

Security headers

6/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

ValidYes
IssuerC=US, O=Let's Encrypt, CN=E7
Expires2026-08-08
Days until expiry44 days

Why it matters: A valid, non-expired certificate ensures encryption is trusted by browsers.

To improve your grade

  • Improve: Modern TLS (no 1.0/1.1) (+10 pts).

Get a weekly security report for this domain

We'll check SSL grade, HTTPS, redirects, and security headers weekly. Email only when something changes.

for captn.cc
Grade breakdown1 thing to improve for a higher grade →
90/100 pts
HTTPS Connection
+25/25
HTTP to HTTPS Redirect
+20/20
Valid SSL Certificate
+20/20
Certificate Not Expiring Soon
+10/10
Short Redirect Chain
+5/5
HSTS Enabled
+5/5
Security Headers
+5/5
Modern TLS (no 1.0/1.1)
+0/10

To improve your grade

  • Improve: Modern TLS (no 1.0/1.1) (+10 pts).

Security headers6/6

  • HSTS
  • CSP
  • X-Frame-Options
  • X-Content-Type-Options
  • Referrer-Policy
  • Permissions-Policy

Score: 6 of 6 headers present. For the grade factor (5 pts), 4+ headers and Content-Security-Policy (CSP) are both required.

HSTS (HTTP Strict Transport Security)Enabled

  • EnabledYes
  • Max-Age365 days
  • PreloadNo
Submit or verify on hstspreload.org

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=86400

Active QUIC negotiation succeeded (curl --http3).

DNS Security

CAA: Not set · DNSSEC: Not signedExpand
CAANot set
DNSSEC
Not signed

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 chain615ms 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. 1.http://captn.cc382ms
  2. 2.https://captn.cc/233ms

Recommendations for captn.cc

Based on this scan, here is the next step that would most improve security and SEO for captn.cc.

  1. Add a CAA DNS record

    Nice to have

    captn.cc 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.

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:

SSL grade badge for captn.cc← live preview, updates automatically
<a href="https://httpsornot.com/report/captn.cc?utm_source=badge" target="_blank" rel="noopener">
  <img src="https://httpsornot.com/badge/captn.cc.svg" alt="SSL grade for captn.cc — checked by HTTPS Checker" height="20" loading="lazy" />
</a>

Domain owner? If you want this report removed or made private, contact us.