HTTPS, SSL & Security Report for saintisidore.org

This report summarizes how well saintisidore.org 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 secureScore45/100Last checked: 18 Aug 2026 at 19:23 UTC
HTTPS

Enabled

HTTP → HTTPS

No

TLS

F · 1.2, 1.3

Security headers

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

No redirect from HTTP to HTTPS was detected.

How to fix: Configure your server (Nginx, Apache, or host) to 301/302 redirect http:// to https://.

TLS & CertificateF

ValidNo
IssuerC=GB, O=Sectigo Limited, CN=Sectigo RSA Domain Validation Secure Server CA
Expires2022-09-12
Days until expiry-1436 days

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

To improve your grade

  • Fix the SSL certificate to improve the grade.

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 breakdown1 thing to improve for a higher grade →
45/100 pts
HTTPS Connection
+25/25
HTTP to HTTPS Redirect
+0/20
Valid SSL Certificate
+0/20
Certificate Not Expiring Soon
+0/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

  • Fix the SSL certificate to improve the grade.

Security headers3/6

  • HSTS
  • CSP
  • X-Frame-Options
  • X-Content-Type-Options
  • Referrer-Policy — sent, but weakSent as "no-referrer-when-downgrade", which sends the full URL — path and query — to other sites. Browsers already default to strict-origin-when-cross-origin when no header is set — use that or no-referrer.
  • Permissions-Policy

Score: 3 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
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 chain1233ms 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://saintisidore.org1175ms
  2. 2.http://stisidores-priory.com/en58ms

Recommendations for saintisidore.org

Based on this scan, here are the 4 next steps that would most improve security and SEO for saintisidore.org.

  1. Set up an HTTP → HTTPS redirect

    High impact

    saintisidore.org 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.

  2. Fix the SSL certificate

    High impact

    The certificate for saintisidore.org is expired. Browsers show a full-page warning for invalid certificates, which drives most visitors away immediately.

  3. Add 3 missing security headers

    Recommended

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

  4. Add a CAA DNS record

    Nice to have

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

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