SSL Check WHOIS
Dashboard / Security Report

laposte.com

IPv6: no public AAAA record — the domain is reachable over IPv4 only.
A+

Exceptional Security

Overall Rating
178.213.66.203 · WHOIS ›
Assessed 2026-11-18 02:06 UTC

Grade Breakdown

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

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)
laposte.com302 → https://laposte.com/ → … → https://www.laposte.fr/ → 200 OK301 → https://www.laposte.fr/ → 200 OK
www.laposte.com301 → https://www.laposte.fr/ → 200 OK301 → https://www.laposte.fr/ → 200 OK
  • http://laposte.com redirects to HTTPS.
  • https://laposte.com forwards visitors to www.laposte.fr, a different site. View its report ›

DNS Records

As a public resolver answered for laposte.com. Looked up 2026-11-18 02:06 UTC · today

TypeRecords
A
AAAA None
NS
ns1.laposte.fr ns2.laposte.net ns3.laposte.net ns4.laposte.net ns5.laposte.fr ns6.laposte.org ns7.laposte.eu
MX
100 rpi0i691.laposte.fr 100 rpi0i693.laposte.fr 100 rpi0i751.laposte.fr 100 rpi0i753.laposte.fr
SPF
v=spf1 include:_spfstd_sccc.laposte.fr include:_spfmm_sccc.laposte.fr include:_spfal_sccc.laposte.fr include:_spftmp_sccc.laposte.fr mx -all

Certificate Identity

Common Namelaposte.com
Alt Names origine-a5d6t7h7d8s9t4f6.prod.net.extra.laposte.fr laposte.com laposte.fr api.boutique.laposte.fr www.laposte.fr
IssuerCN=GlobalSign GCC R3 EV TLS CA 2025, O=GlobalSign nv-sa, C=BE
Validity 2026-06-09 to 2026-12-25 (37 days remaining)
KeyRSA 4096 bits (sha256RSA)
Serial Number11DBE5DDFF75350226F36E14
SHA256 Fingerprint 99cd64d5be306220d9e39acab1c9bfb72ce2812fa7a0c2368e23e12315001bf3
Pin SHA256HEKz1DsJWrzoOWl1XVPhkl8XsiLipqDJFGfMi919vtI=

Certificate Properties

Type EV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Unknown (OCSP-only certificate; not queried) OCSP: http://ocsp.globalsign.com/gsgccr3evtlsca2025
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 199 days (maximum 200 days for certificates issued then)
Chain Issues
• Contains anchor (root CA included in chain)

Protocol Configuration

Supported Protocols

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

Negotiated Cipher

TLS_AES_128_GCM_SHA256

Protocol Details

Connection
ALPN No
SNI Required No
Supported Named Groups secp256r1 x25519 secp384r1 ffdhe3072 (server preference order)
Post-Quantum Key Exchange No (no hybrid ML-KEM group such as X25519MLKEM768)
HTTP/3 (QUIC) No
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
HSTS No
HSTS Preloading N/A (HSTS not enabled)
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 (server-preferred order)
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2 (server-preferred order)
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384 Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384 Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384 Success
iOS 17 / SafariTLS 1.3TLS_CHACHA20_POLY1305_SHA256 Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384 Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256 Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
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.

Trust Chain Architecture

End-Entity Certificate
CN=origine-a5d6t7h7d8s9t4f6.prod.net.extra.laposte.fr, O=LA POSTE SA, L=Paris, S=Île-de-France, C=FR, jurisdictionCountryName=FR, SERIALNUMBER=356 000 000, businessCategory=Private Organization (Issuer: CN=GlobalSign GCC R3 EV TLS CA 2025, O=GlobalSign nv-sa, C=BE)
Intermediate CA
CN=GlobalSign GCC R3 EV TLS CA 2025, O=GlobalSign nv-sa, C=BE (Issuer: CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3)
Root Certificate
CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3 (Issuer: CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3)

TLS History & Relations

Everything our scans have seen for laposte.com, first seen 2026-10-09; current certificate since 2026-11-18.

Certificates served

Certificate (SHA-256)IssuerValidServed
99cd64d5be306220… current GlobalSign GCC R3 EV TLS CA 20252026-06-09 → 2026-12-252026-11-18

Addresses

AddressCertificateSeen
178.213.66.203 99cd64d5be306220… 2026-11-18

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-18 02:06A+TLS 1.3 99cd64d5be306220… 178.213.66.203

Other domains on the same certificate

Other hosts seen on the same addresses