SSL Check WHOIS
Dashboard / Security Report

www.burgerking.es

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
A+ 3.162.38.114 IPv4 WHOIS › A+ 3.162.38.29 IPv4 WHOIS › A+ 3.162.38.32 IPv4 WHOIS › A+ 3.162.38.60 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-08 22:40 UTC

Grade Breakdown

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

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 — shown as unknown, not as unsupported
Downgrade Prevention Yes (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling Yes
HSTS Yes 2 years · includeSubDomains · preload
HSTS Preloading Not preloadedSubmit →
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
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_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak

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.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.

Hosthttp:// (port 80)https:// (port 443)
www.burgerking.es301 → https://www.burgerking.es/ → 200 OK200 OK
burgerking.es301 → https://burgerking.es/ → … → https://www.burgerking.es/ → 200 OK301 → https://www.burgerking.es/ → 200 OK
  • http://www.burgerking.es redirects to HTTPS.

DNS Records

As a public resolver answered for www.burgerking.es and its domain burgerking.es. Looked up 2026-11-08 22:40 UTC · 8 days ago

TypeRecords
www.burgerking.es
A
AAAA None
MX None
SPF None
burgerking.es
A
AAAA None
NS
udns1.cscdns.net udns2.cscdns.uk
MX
10 mx.burgerking.es
SPF
v=spf1 include:amazonses.com exists:%{i}._spf.sparkpostmail.com ~all

Certificate Identity

Common Namewww.burgerking.es
Alt Names burgerking.es prod-bk-es-web.rbi.tools prod-bk-web.es.rbi.tools whopper.burgerking.es *.prod-bk-web.es.rbi.tools prod.web.bk.es.rbi.tools www.burgerking.es
IssuerCN=Amazon RSA 2048 M04, O=Amazon, C=US
Validity 2026-10-18 to 2027-05-03 (167 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number02E51F59AF5A042262AB1353FB3F2199
SHA256 Fingerprint 49375f09eb4b53ba708143aee2390c63e42d54270553ae6c782da33036005358
Pin SHA2567hgNqWAWhuLyC9zVtdNgzTFofik7LPkYE17GMbldpHg=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.r2m04.amazontrust.com CRL: http://crl.r2m04.amazontrust.com/r2m04.crl
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 198 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=burgerking.es (Issuer: CN=Amazon RSA 2048 M04, O=Amazon, C=US)
Intermediate CA
CN=Amazon RSA 2048 M04, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)
Root Certificate
CN=Amazon Root CA 1, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)

TLS History & Relations

Everything our scans have seen for www.burgerking.es, first seen 2026-11-06; current certificate since 2026-11-08.

Certificates served

Certificate (SHA-256)IssuerValidServed
49375f09eb4b53ba… current Amazon RSA 2048 M042026-10-18 → 2027-05-032026-11-08

Addresses

AddressCertificateSeen
3.162.38.29 49375f09eb4b53ba… 2026-11-08
3.162.38.32 49375f09eb4b53ba… 2026-11-08
3.162.38.60 49375f09eb4b53ba… 2026-11-08
3.162.38.114 49375f09eb4b53ba… 2026-11-08

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-08 22:40A+TLS 1.3 49375f09eb4b53ba… 3.162.38.29, 3.162.38.32, 3.162.38.60, 3.162.38.114

Other domains on the same certificate

Other hosts seen on the same addresses