HTTPS Checker

Security Tool

HTTPS, SSL & Security Report for ariff.website

This report summarizes how well ariff.website 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.

Partially secureScore75/100Last checked: 10 Jul 2026 at 17:19 UTC
HTTPS

Enabled

HTTP → HTTPS

N/A

TLS

B · 1.2, 1.3

Security headers

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

HTTP port 80 is not responding, so there is no HTTP listener to redirect. Modern browsers upgrade to HTTPS automatically.

Note: Port 80 may be firewalled or intentionally closed. Opening it with a 301 to HTTPS ensures visitors who type http:// are redirected rather than getting a connection error.

TLS & CertificateB

ValidYes
IssuerC=US, O=Let's Encrypt, CN=R12
Expires2026-08-16
Days until expiry36 days

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

To improve your grade

  • •Port 80 is closed, so visitors typing http:// get a connection error instead of an automatic redirect. Open port 80 with a 301 to HTTPS to recover the redirect points.
  • •Reach 80+ points for B+ (currently 75).

Monitor this domain

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

Start monitoring — freeOne-click account with Google, GitHub, or email. No password.

Free: 1 domain, weekly. Plans from €7/mo — daily checks, up to 50 domains, history & white-label PDF.

Grade breakdown2 things to improve for a higher grade →
75/100 pts
HTTPS Connection
+25/25
HTTP to HTTPS Redirect
+0/20
Valid SSL Certificate
+20/20
Certificate Not Expiring Soon
+10/10
Short Redirect Chain
+5/5
HSTS Enabled
+5/5
Security Headers
+0/5

Requires 4 of 6 headers and Content-Security-Policy (CSP).

Modern TLS (no 1.0/1.1)
+10/10

To improve your grade

  • •Port 80 is closed, so visitors typing http:// get a connection error instead of an automatic redirect. Open port 80 with a 301 to HTTPS to recover the redirect points.
  • •Reach 80+ points for B+ (currently 75).

Security headers4/6

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

Score: 4 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)Preload ready

  • EnabledYes
  • Max-Age365 days
  • PreloadYes
  • On HSTS preload listNo
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/3 (QUIC)

Not advertised

The server does not advertise HTTP/3 (QUIC) via the Alt-Svc header.

DNS Security

CAA: Not set · DNSSEC: Not signed · HTTPS record: Not setExpand
CAANot set
DNSSEC
Not signed
HTTPS Record
Not set

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.

Redirect chain

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://ariff.website

Recommendations for ariff.website

Based on this scan, here are the 5 next steps that would most improve security and SEO for ariff.website.

  1. Set up an HTTP → HTTPS redirect

    High impact

    ariff.website does not redirect plain HTTP requests to HTTPS. Visitors (and search engines) landing on the HTTP version get an insecure page, and you may be splitting SEO signals between two versions of the site. A single 301 redirect fixes both.

    How to fix HTTP to HTTPS redirect Re-test the redirect

  2. Add 2 missing security headers

    Recommended

    ariff.website sends 4 of 6 recommended security headers — missing: CSP, Permissions-Policy. Most take one line of server config and protect against clickjacking, MIME sniffing and data leaks.

    How to set security headers What each header does

  3. Consider HSTS preload

    Nice to have

    HSTS is enabled for ariff.website but the domain is not on the browser preload list, so the very first visit can still go over HTTP. Preloading closes that gap — but read the requirements first, removal is slow.

    How to submit (and safely remove) HSTS preload

  4. Consider HTTP/3

    Nice to have

    ariff.website supports HTTP/2 but does not advertise HTTP/3 (QUIC). HTTP/3 improves performance on lossy mobile networks. If you are behind Cloudflare or a modern CDN it is usually a toggle.

    How to enable HTTP/2 and HTTP/3 Why HTTP/3 detection tools disagree

  5. Add a CAA DNS record

    Nice to have

    ariff.website 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.

    What is a CAA record

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

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

Check another domain