SSL Check WHOIS
Dashboard / Security Report

follow.fr

Add this badge to your site

Shows this report's grade and links back to it. It is read from the stored report, never a new scan; a report older than 30 days also shows the month it was checked.

follow.fr: SSL/TLS grade A+ (HTTPS Monitor)follow.frA+
Overall grade based on: IPv4: 1 of 3 complete, 2 unreachable · IPv6: none
1 different configuration detected across 3 endpoints Select an IP for owner, ASN & location
— 2 unreachable
A+ 198.202.211.1 IPv4 WHOIS ›
⚡
75.2.70.75 WHOIS › IPv4 — Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “internal_error”.
⚡
99.83.190.102 WHOIS › IPv4 — Port 443 accepted the connection, but no TLS handshake was completed: the server answered with the TLS alert “internal_error”.
A+

Exceptional Security

Overall Rating
Assessed 2026-11-22 03:42 UTC

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%

Protocol Configuration

Supported Protocols

TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3
SSL 2

Negotiated Cipher

TLS_AES_256_GCM_SHA384

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups X25519MLKEM768 X25519Kyber768Draft00 x25519 secp256r1 secp384r1 secp521r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, X25519Kyber768Draft00
HTTP/3 (QUIC) Yes (advertised)
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Downgrade Prevention Yes (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No (certificate has no OCSP responder)
HSTS Yes 1 year
HSTS Preloading Not preloadedSubmit →
Security Checks
BEAST attack Mitigated
POODLE (SSLv3) No (SSL 3 not supported)
POODLE (TLS) No
RC4 No
SSL/TLS CompressionNo (not supported by .NET TLS stack)
HeartbleedNot tested

Cipher Suite Analysis

Cipher SuiteHexKey ExchangeFSBitsStrength
# TLS 1.3
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA2560xC02BECDHEFS128Secure
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA3840xC02CECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA2560xCCA9ECDHEFS256Secure

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
iOS 17 / SafariTLS 1.3TLS_CHACHA20_POLY1305_SHA256Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 4.0.4--No
Android 4.1.1--No
Baidu Jan 2015--No
Java 6--No

* Simulated based on server's supported protocols and cipher configuration.

Site Access: HTTP and HTTPS

What a visitor typing each address gets, and where its redirects end (up to 5 are followed), as seen from our scanner.

Hosthttp:// (port 80)https:// (port 443)
follow.fr301 → https://follow.fr/ → TLS handshake failedTLS handshake failed
www.follow.fr301 → https://www.follow.fr/ → 200 OK200 OK
  • http://follow.fr redirects to HTTPS.

DNS Records

As a public resolver answered for follow.fr. Looked up 2026-11-22 03:42 UTC · today

TypeRecords
A
AAAA None
NS
ns-143-b.gandi.net ns-188-a.gandi.net ns-191-c.gandi.net
MX
1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx3.googlemail.com
SPF
v=spf1 ip4:91.247.75.141 include:_spf.google.com include:spf.sendinblue.com include:26125804.spf07.hubspotemail.net ~all

Certificate Identity

Common Namefollow.fr
Alt Names follow.fr
IssuerCN=WE1, O=Google Trust Services, C=US
Validity 2026-10-28 to 2027-01-26 (65 days remaining)
KeyECDSA 256 bits (sha256ECDSA)
Serial Number00E27AC1BF6BB27DB1132E66D17F7F7E11
SHA256 Fingerprint 7e1a8492b0d750df5dd060955f13debb222b06d67cc16c795296eb5d8cc18e3a
Pin SHA256tllPJcHVhd6Z6tgRd6vsnGFvDP8zbcUyvwZstio1+BU=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://c.pki.goog/we1/ndRtg9VW_VQ.crl No OCSP responder — revocation is published via CRL only (as CA/B Forum rules now allow).
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 90 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=follow.fr (Issuer: CN=WE1, O=Google Trust Services, C=US)
Intermediate CA
CN=WE1, O=Google Trust Services, C=US (Issuer: CN=GTS Root R4, O=Google Trust Services LLC, C=US)
Root Certificate
CN=GTS Root R4, O=Google Trust Services LLC, C=US (Issuer: CN=GTS Root R4, O=Google Trust Services LLC, C=US)

TLS History & Relations

Everything our scans have seen for follow.fr, first seen 2026-11-22; current certificate since 2026-11-22.

Certificates served

Certificate (SHA-256)IssuerValidServed
7e1a8492b0d750df… current WE12026-10-28 → 2027-01-262026-11-22

Addresses

AddressCertificateSeen
75.2.70.75 no TLS 2026-11-22
99.83.190.102 no TLS 2026-11-22
198.202.211.1 7e1a8492b0d750df… 2026-11-22

TLS history (a row per change; repeated checks only extend it)

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-22 03:42A+TLS 1.3 7e1a8492b0d750df… 75.2.70.75, 99.83.190.102, 198.202.211.1

Other hosts seen on the same addresses