f1g.fr
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
Grade Breakdown
Protocol Support 50%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Grade capped at B: server supports obsolete TLS 1.0/1.1.
Security Vulnerabilities Detected
- •Obsolete TLS versions (1.0/1.1) supported.
- •CBC cipher suites with TLS 1.0/1.1 (BEAST, Lucky13).
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.
| Host | http:// (port 80) | https:// (port 443) |
|---|---|---|
| f1g.fr | 200 OK (unencrypted) | 200 OK |
| www.f1g.fr | Does not resolve | Does not resolve |
- http://f1g.fr answers without redirecting to HTTPS: visitors who type the address without https:// get an unencrypted page.
- www.f1g.fr does not resolve: visitors who type it reach nothing.
DNS Records
As a public resolver answered for f1g.fr. Looked up 2026-11-18 03:47 UTC · today
| Type | Records |
|---|---|
| A | |
| AAAA | None |
| NS | a1-194.akam.net a16-64.akam.net a2-67.akam.net a3-64.akam.net a5-67.akam.net a8-65.akam.net |
| MX | 0 mx3.nameshield.com 10 mx4.nameshield.net |
| SPF | None |
Certificate Identity
| Common Name | f1g.fr |
| Alt Names | a.f1g.fr app-partner.s.f1g.fr assets.s.f1g.fr f1g.fr faq.leparticulier.lefigaro.fr i.f1g.fr lefigaro.preview.f1g.fr p.f1g.fr |
| Issuer | CN=YR2, O=Let's Encrypt, C=US |
| Validity | 2026-11-03 to 2027-02-01 (75 days remaining) |
| Key | RSA 2048 bits (sha256RSA) |
| Serial Number | 066C5A6B99DC3E27BD392B9241181B7AF002 |
| SHA256 Fingerprint | b8d5351147e70714f7121844f9a3985ecfb593f053373ed886927124207766b0 |
| Pin SHA256 | Tm0Zk/zB4LoGVgv20SpoOnizD3It5xt/IE2aPgRU0VM= |
Certificate Properties
| Type | DV |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) CRL: http://yr2.c.lencr.org/3.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 Issues | None |
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 | No |
| Supported Named Groups | X25519MLKEM768 x25519 secp256r1 (server preference order) |
| Post-Quantum Key Exchange | Yes X25519MLKEM768 |
| HTTP/3 (QUIC) | No |
| Encrypted Client Hello | No |
| Security Features | |
| Forward Secrecy | Yes (ECDHE / DHE) |
| Downgrade Prevention | Yes (TLS_FALLBACK_SCSV) |
| Secure Renegotiation | Supported (RFC 5746) |
| Extended Master Secret | Yes (RFC 7627) |
| OCSP Stapling | No (certificate has no OCSP responder) |
| HSTS | No |
| HSTS Preloading | N/A (HSTS not enabled) |
| Security Checks | |
| BEAST attack | Not mitigated server-side (TLS 1.0 + CBC) |
| POODLE (SSLv3) | No (SSL 3 not supported) |
| POODLE (TLS) | Possible (CBC + legacy TLS present) |
| RC4 | No |
| SSL/TLS Compression | No (not supported by .NET TLS stack) |
| Heartbleed | Not tested |
Cipher Suite Analysis
| Cipher Suite | Hex | Key Exchange | FS | Bits | Strength |
|---|---|---|---|---|---|
| # TLS 1.3 (server-preferred order) | |||||
| TLS_AES_256_GCM_SHA384 | 0x1302 | ECDHE | FS | 256 | Secure |
| TLS_CHACHA20_POLY1305_SHA256 | 0x1303 | ECDHE | FS | 256 | Secure |
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| TLS_AES_128_CCM_SHA256 | 0x1304 | ECDHE | FS | 128 | Secure |
| # TLS 1.2 (server-preferred order) | |||||
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | 0xC02F | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA8 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 | 0xC028 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 | 0xC027 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | 0xC014 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | 0xC013 | ECDHE | FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_GCM_SHA384 | 0x009D | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_GCM_SHA256 | 0x009C | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_CBC_SHA256 | 0x003D | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_CBC_SHA256 | 0x003C | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_CBC_SHA | 0x0035 | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_CBC_SHA | 0x002F | RSA | No FS | 128 | Weak |
Handshake Simulation
| Client | Protocol | Cipher Suite | Result |
|---|---|---|---|
| Chrome 120 / Win 11 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Chrome 80 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Firefox 115 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| iOS 17 / Safari | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 | Success |
| macOS 14 / Safari | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Android 14 | TLS 1.3 | TLS_AES_128_GCM_SHA256 | Success |
| Chrome 69 / Win 7 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Chrome 49 / XP SP3 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 10 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 7 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 9.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 7.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 5.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 4.4.2 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 11 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 8u121 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 4.0.4 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | Success |
| Android 4.1.1 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | Success |
| Baidu Jan 2015 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | Success |
| Java 6 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | Success |
* Simulated based on server's supported protocols and cipher configuration.
Trust Chain Architecture
End-Entity Certificate
CN=a.f1g.fr (Issuer: CN=YR2, O=Let's Encrypt, C=US)
Intermediate CA
CN=YR2, O=Let's Encrypt, C=US (Issuer: CN=Root YR, O=ISRG, C=US)
Intermediate CA
CN=Root YR, O=ISRG, C=US (Issuer: CN=ISRG Root X1, O=Internet Security Research Group, C=US)
Root Certificate
CN=ISRG Root X1, O=Internet Security Research Group, C=US (Issuer: CN=ISRG Root X1, O=Internet Security Research Group, C=US)
TLS History & Relations
Everything our scans have seen for f1g.fr, first seen 2026-06-09; current certificate since 2026-11-18.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| b8d5351147e70714… current | YR2 | 2026-11-03 → 2027-02-01 | 2026-11-18 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 23.219.248.40 | b8d5351147e70714… | 2026-11-18 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-18 03:47 | B | TLS 1.3 | b8d5351147e70714… | 23.219.248.40 |
Other domains on the same certificate
- lefigaro.fr 1 name