SSL Check WHOIS
Dashboard / Security Report

espn.com.pe

IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 4 endpoints share identical configuration Select an IP for owner, ASN & location
B 13.249.228.105 IPv4 WHOIS › B 13.249.228.121 IPv4 WHOIS › B 13.249.228.58 IPv4 WHOIS › B 13.249.228.74 IPv4 WHOIS ›
B

Adequate Protection

Overall Rating
Assessed 2026-10-30 22:20 UTC

Grade Breakdown

Protocol Support 50%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Certificate has expired. This domain's SSL/TLS certificate is no longer valid and browsers will show security warnings to visitors.
Grade capped at B: server supports obsolete TLS 1.0/1.1.

Security Vulnerabilities Detected

  • •Obsolete TLS versions (1.0/1.1) supported.
  • •Weak 3DES cipher supported (Sweet32).
  • •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_128_GCM_SHA256

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups X25519MLKEM768 SecP256r1MLKEM768 x25519 secp256r1 secp384r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, SecP256r1MLKEM768
HTTP/3 (QUIC) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Scan Coverage Incomplete no answer in time for: key exchange groups, TLS_FALLBACK_SCSV — shown as unknown, not as unsupported
Downgrade Prevention Unknown
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling Yes
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 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_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_RSA_WITH_AES_128_GCM_SHA2560x009CRSANo FS128Weak
TLS_RSA_WITH_AES_256_GCM_SHA3840x009DRSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA2560x003CRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA0x002FRSANo FS128Weak
TLS_RSA_WITH_3DES_EDE_CBC_SHA0x000ARSANo FS112Weak

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_RSA_WITH_AES_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 4.0.4TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHASuccess
Android 4.1.1TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHASuccess
Baidu Jan 2015TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHASuccess
Java 6TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHASuccess

* 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)
espn.com.pe202 Accepted (unencrypted)202 Accepted
www.espn.com.pe202 Accepted (unencrypted)202 Accepted
  • http://espn.com.pe answers without redirecting to HTTPS: visitors who type the address without https:// get an unencrypted page.
  • http://www.espn.com.pe answers without redirecting to HTTPS.

Certificate Identity

Common Nameespn.com.pe
Alt Names editions.espn.com *.api.espn.cl *.api.espn.co.cr *.api.espn.co.uk *.api.espn.com.ar *.api.espn.com.au *.api.espn.com.br *.api.espn.com.co *.api.espn.com.do *.api.espn.com.ec *.api.espn.com.gt *.api.espn.com.mx *.api.espn.com.pa *.api.espn.com.pe *.api.espn.com.sg *.api.espn.com.uy *.api.espn.com.ve *.api.espn.es *.api.espn.in *.api.espn.nl *.espn.cl *.espn.co.cr *.espn.co.uk *.espn.com *.espn.com.ar *.espn.com.au *.espn.com.br *.espn.com.co *.espn.com.do *.espn.com.ec *.espn.com.gt *.espn.com.mx *.espn.com.pa *.espn.com.pe *.espn.com.sg *.espn.com.uy *.espn.com.ve *.espn.es *.espn.go.com *.espn.in *.espn.nl *.espn.ph *.espndeportes.com *.fan.api.espn.co.cr *.fan.api.espn.com.do *.fan.api.espn.com.ec *.fan.api.espn.com.gt *.fan.api.espn.com.pa *.fan.api.espn.com.pe *.fan.api.espn.com.sg *.fan.api.espn.com.uy *.fan.api.espn.com.ve *.fan.api.espn.es *.fan.api.espn.nl *.fan.api.espn.ph espn.cl espn.co.cr espn.co.uk espn.com espn.com.ar espn.com.au espn.com.br espn.com.co espn.com.do espn.com.ec espn.com.gt espn.com.mx espn.com.pa espn.com.pe espn.com.sg espn.com.uy espn.com.ve espn.es espn.go.com espn.in espn.nl espn.ph espndeportes.com fan.core.api.espn.cl fan.core.api.espn.co.cr fan.core.api.espn.co.uk fan.core.api.espn.com.ar fan.core.api.espn.com.au fan.core.api.espn.com.br fan.core.api.espn.com.co fan.core.api.espn.com.do fan.core.api.espn.com.ec fan.core.api.espn.com.gt fan.core.api.espn.com.mx fan.core.api.espn.com.pa fan.core.api.espn.com.pe fan.core.api.espn.com.sg fan.core.api.espn.com.uy fan.core.api.espn.com.ve fan.core.api.espn.es fan.core.api.espn.in fan.core.api.espn.nl fan.core.api.espn.ph
IssuerCN=Sectigo Public Server Authentication CA OV R36, O=Sectigo Limited, C=GB
Validity 2025-11-10 to 2026-11-10 (6 days ago — expired)
KeyRSA 2048 bits (sha256RSA)
Serial Number07390F4762AA71FDE5C8106A61450B79
SHA256 Fingerprint dd779a75dd1dee204671f511091cda82ec0e52f125176ef5ce4683c374407904
Pin SHA256i+2gQCBo4n/ez0i6nSYMetgv+FX4qlj3m7Qq0PJlr2o=

Certificate Properties

Type OV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.sectigo.com CRL: http://crl.sectigo.com/SectigoPublicServerAuthenticationCAOVR36.crl
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 366 days (maximum 398 days for certificates issued then)
Chain Issues
• Contains anchor (root CA included in chain)

Trust Chain Architecture

End-Entity Certificate
CN=editions.espn.com, O=The Walt Disney Company, S=California, C=US (Issuer: CN=Sectigo Public Server Authentication CA OV R36, O=Sectigo Limited, C=GB)
Intermediate CA
CN=Sectigo Public Server Authentication CA OV 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 espn.com.pe, first seen 2026-04-13; current certificate since 2026-10-30.

Certificates served

Certificate (SHA-256)IssuerValidServed
dd779a75dd1dee20… current Sectigo Public Server Authentication CA OV R362025-11-10 → 2026-11-102026-10-30

Addresses

AddressCertificateSeen
13.249.228.58 dd779a75dd1dee20… 2026-10-30
13.249.228.74 dd779a75dd1dee20… 2026-10-30
13.249.228.105 dd779a75dd1dee20… 2026-10-30
13.249.228.121 dd779a75dd1dee20… 2026-10-30

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-10-30 22:20BTLS 1.3 dd779a75dd1dee20… 13.249.228.58, 13.249.228.74, 13.249.228.105, 13.249.228.121
2026-10-30 22:20BTLS 1.3 dd779a75dd1dee20… 13.249.228.58, 13.249.228.74, 13.249.228.105, 13.249.228.121

Other domains on the same certificate

Other hosts seen on the same addresses