fcbarcelona.cn
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 2 endpoints share identical configuration Select an IP for owner, ASN & location
F 16.162.201.180 IPv4 WHOIS › F 16.163.181.87 IPv4 WHOIS › Grade Breakdown
Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 0%
Certificate has expired. This domain's SSL/TLS certificate is no longer valid and browsers will show security warnings to visitors.
Certificate is expired.
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 | x25519 secp256r1 secp384r1 secp521r1 (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 Secrecy | Yes (ECDHE / DHE) |
| Downgrade Prevention | Yes (legacy TLS disabled) |
| Secure Renegotiation | Supported (RFC 5746) |
| Extended Master Secret | Yes (RFC 7627) |
| OCSP Stapling | No |
| HSTS | Unknown (the HTTPS request to this IP failed) |
| 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 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_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 1.2 | |||||
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | ECDHE | FS | 256 | Secure |
| TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 | 0x009F | DHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA8 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | 0xC02F | ECDHE | FS | 128 | Secure |
| TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 | 0x009E | DHE | FS | 128 | Secure |
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 | - | - | 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.
| Host | http:// (port 80) | https:// (port 443) |
|---|---|---|
| fcbarcelona.cn | 301 → https://fcbarcelona.cn/ → 200 OK | 200 OK · certificate expired |
| www.fcbarcelona.cn | 301 → https://www.fcbarcelona.cn/ → 200 OK | 200 OK · certificate expired |
- http://fcbarcelona.cn redirects to HTTPS.
- www.fcbarcelona.cn serves an expired certificate: browsers show a security warning there.
DNS Records
As a public resolver answered for fcbarcelona.cn. Looked up 2026-11-17 10:45 UTC · today
| Type | Records |
|---|---|
| A | |
| AAAA | None |
| NS | ns-1447.awsdns-52.org ns-1649.awsdns-14.co.uk ns-175.awsdns-21.com ns-851.awsdns-42.net |
| MX | None |
| SPF | None |
Certificate Identity
| Common Name | fcbarcelona.cn |
| Alt Names | www.fcbarcelona.cn fcbarcelona.cn |
| Issuer | CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB |
| Validity | 2026-04-23 to 2026-11-07 (9 days ago — expired) |
| Key | RSA 2048 bits (sha256RSA) |
| Serial Number | 1AFDA9A4CD02EC33C9DE8C7DBCAE33B9 |
| SHA256 Fingerprint | aecb4e725f98d68d6979ecb2158647be1e745ae8d9074f5aefd163e1ee41bfab |
| Pin SHA256 | 4ww3gqReADuR1XjZkSEA5ngO6mc+MeurqnijX+n9+9E= |
Certificate Properties
| Type | DV |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Unknown (OCSP-only certificate; not queried) OCSP: http://ocsp.sectigo.com |
| DNS CAA | No (missing) |
| Trusted By | Not verified |
| Name Match | Yes |
| Validity Period | 199 days (maximum 200 days for certificates issued then) |
| Chain Issues | None |
Trust Chain Architecture
End-Entity Certificate
CN=www.fcbarcelona.cn (Issuer: CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB)
Intermediate CA
CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB (Issuer: CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB)
Root Certificate
CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB (Issuer: CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB)
TLS History & Relations
Everything our scans have seen for fcbarcelona.cn, first seen 2026-08-02; current certificate since 2026-11-17.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| aecb4e725f98d68d… current | Sectigo Public Server Authentication CA DV R36 | 2026-04-23 → 2026-11-07 | 2026-11-17 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 16.162.201.180 | aecb4e725f98d68d… | 2026-11-17 |
| 16.163.181.87 | aecb4e725f98d68d… | 2026-11-17 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-17 10:45 | F | TLS 1.3 | aecb4e725f98d68d… | 16.162.201.180, 16.163.181.87 |