cdn-besancon.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.
Overall grade based on: IPv4: 2 of 2 complete · IPv6: 2 of 2 complete
All 4 endpoints share identical configuration Select an IP for owner, ASN & location
B 104.21.48.9 IPv4 WHOIS › B 172.67.175.178 IPv4 WHOIS › B 2606:4700:3035::ac43:afb2 IPv6 WHOIS › B 2606:4700:3036::6815:3009 IPv6 WHOIS › 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).
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 | Yes(ECH config in HTTPS DNS record) |
| 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 | |||||
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| TLS_AES_256_GCM_SHA384 | 0x1302 | ECDHE | FS | 256 | Secure |
| TLS_CHACHA20_POLY1305_SHA256 | 0x1303 | ECDHE | FS | 256 | Secure |
| # TLS 1.2 | |||||
| TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | 0xC02B | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA9 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA | 0xC009 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | 0xC02C | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA | 0xC00A | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 | 0xC023 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 | 0xC024 | ECDHE | FS | 256 | 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_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Chrome 49 / XP SP3 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| IE 11 / Win 10 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| IE 11 / Win 7 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 9.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 7.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 5.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 4.4.2 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Java 11 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Java 8u121 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 4.0.4 | TLS 1.0 | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA | Success |
| Android 4.1.1 | TLS 1.0 | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA | Success |
| Baidu Jan 2015 | TLS 1.0 | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA | Success |
| Java 6 | TLS 1.0 | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA | Success |
* 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.
| Host | http:// (port 80) | https:// (port 443) |
|---|---|---|
| cdn-besancon.fr | 301 → https://www.cdn-besancon.fr/ → 200 OK | 301 → https://www.cdn-besancon.fr/ → 200 OK |
| www.cdn-besancon.fr | 301 → https://cdn-besancon.fr/ → … → https://www.cdn-besancon.fr/ → 200 OK | 200 OK |
- http://cdn-besancon.fr redirects to HTTPS.
DNS Records
As a public resolver answered for cdn-besancon.fr. Looked up 2026-11-18 13:27 UTC · 2 days ago
| Type | Records |
|---|---|
| A | |
| AAAA | |
| NS | kelly.ns.cloudflare.com lennon.ns.cloudflare.com |
| MX | 10 mx10.antispam.mailspamprotection.com 20 mx20.antispam.mailspamprotection.com 30 mx30.antispam.mailspamprotection.com |
| SPF | v=spf1 +a +mx include:cdn-besancon.fr.spf.auto.dnssmarthost.net ~all |
Certificate Identity
| Common Name | cdn-besancon.fr |
| Alt Names | cdn-besancon.fr *.cdn-besancon.fr |
| Issuer | CN=WE1, O=Google Trust Services, C=US |
| Validity | 2026-11-13 to 2027-02-11 (82 days remaining) |
| Key | ECDSA 256 bits (sha256ECDSA) |
| Serial Number | 00B6C24262382C019F1359DBC51101219B |
| SHA256 Fingerprint | 332764fff14d24e6de4f79020f3232f345c7c2fecdf67a2a7b9df5117d6d659b |
| Pin SHA256 | NPTepCx0z9rYq4aoC+rqUei4VY0F61tA6HIDoI4UXug= |
Certificate Properties
| Type | DV Domain Validated |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) CRL: http://c.pki.goog/we1/Xau4Zk7p9lQ.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 |
Trust Chain Architecture
End-Entity Certificate
CN=cdn-besancon.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 cdn-besancon.fr, first seen 2026-11-18; current certificate since 2026-11-18.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 332764fff14d24e6… current | WE1 | 2026-11-13 → 2027-02-11 | 2026-11-18 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 104.21.48.9 | 332764fff14d24e6… | 2026-11-18 |
| 172.67.175.178 | 332764fff14d24e6… | 2026-11-18 |
| 2606:4700:3035::ac43:afb2 | 332764fff14d24e6… | 2026-11-18 |
| 2606:4700:3036::6815:3009 | 332764fff14d24e6… | 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 13:27 | B | TLS 1.3 | 332764fff14d24e6… | 104.21.48.9, 172.67.175.178 |