rosebikes.es
Overall grade based on: IPv4: 2 of 2 complete · IPv6: 0 of 2 complete, 2 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2a02:26f0:3900::211:c639 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a02:26f0:3900::211:c63b IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
The IPv4 report below is complete. IPv6 results will be added to this page automatically when the scan finishes.
All 2 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 2.17.198.57 IPv4 WHOIS › A+ 2.17.198.59 IPv4 WHOIS › 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_256_GCM_SHA384
Protocol Details
| Connection | |
| ALPN | http/1.1 |
| SNI Required | Yes |
| Supported Named Groups | X25519MLKEM768 x25519 secp256r1 (server preference order) |
| Post-Quantum Key Exchange | Yes X25519MLKEM768 |
| HTTP/3 (QUIC) | Yes (advertised) |
| 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 (certificate has no OCSP responder) |
| HSTS | Yes 1 year · 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 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_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | 0xC02F | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA8 | ECDHE | FS | 256 | 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) |
|---|---|---|
| rosebikes.es | 301 → https://rosebikes.es/ → … → https://www.rosebikes.es/es/ → 200 OK | 301 → https://www.rosebikes.es/ → … → https://www.rosebikes.es/es/ → 200 OK |
| www.rosebikes.es | 301 → https://www.rosebikes.es/ → … → https://www.rosebikes.es/es/ → 200 OK | 301 → https://www.rosebikes.es/es/ → 200 OK |
- http://rosebikes.es redirects to HTTPS.
DNS Records
As a public resolver answered for rosebikes.es. Looked up 2026-11-17 07:04 UTC · today
| Type | Records |
|---|---|
| A | |
| AAAA | |
| NS | a1-223.akam.net a14-67.akam.net a2-67.akam.net a20-66.akam.net a7-67.akam.net a9-65.akam.net |
| MX | 0 rosebikes-es.mail.protection.outlook.com |
| SPF | v=spf1 include:spf.protection.outlook.com include:inxserver.com ip4:82.141.40.167 ip4:82.141.40.130 -all |
Certificate Identity
Certificate Properties
| Type | DV |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) CRL: http://yr1.c.lencr.org/34.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=www.rosebikes.de (Issuer: CN=YR1, O=Let's Encrypt, C=US)
Intermediate CA
CN=YR1, 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 rosebikes.es, first seen 2026-10-08; current certificate since 2026-11-17.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| dbc462eaaa10c31a… current | YR1 | 2026-11-05 → 2027-02-03 | 2026-11-17 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 2.17.198.57 | dbc462eaaa10c31a… | 2026-11-17 |
| 2.17.198.59 | dbc462eaaa10c31a… | 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 07:04 | A+ | TLS 1.3 | dbc462eaaa10c31a… | 2.17.198.57, 2.17.198.59 |
Other domains on the same certificate
- rosebikes.de 5 names
- rosebikes.at 3 names
- rosebikes.be 3 names
- rosebikes.co.uk 3 names
- rosebikes.ch 2 names
- rosebikes.com 2 names
- rosebikes.dk 2 names
- rosebikes.fi 2 names
- rosebikes.fr 2 names
- rosebikes.hu 2 names
- rosebikes.ie 2 names
- rosebikes.it 2 names
- rosebikes.nl 2 names
- rosebikes.pl 2 names
- rosebikes.ro 2 names
- rosebikes.se 2 names
- rosebikes.shop 2 names
- rose.de 2 names
- roseversand.de 2 names
Other hosts seen on the same addresses
access.loginpostnl.net accounts.ebay.com activpet.pt alectoums-preprod.mafrservicesstg.com anywhere.ebay.be api-combined-messages.southeasternrailway.co.uk apis.green.dpd.co.uk app-sandbox.internal.communications.staging.bnpparibas ar.ebay.com author-preprod-ap.manulife.com b24.eveplus.net backopsapi.speaking.onlinemarking.britishcouncil.org bodyandsoul.newssit.com.au books.stores.shop.ebay.ca buildyour.landrover.co.nz business-continuity.dpd.co.uk cag.mtr.com.hk carnet.paris-normandie.fr claims-core.cardif.com.co clbrtn.polb.com compliance.sony-mea.com connect.ebay.com connect.ebay.com.sg cr.scdocgen.prod.ext.gwam.manulife.com datacollect.sephora.eu digitale-postzegel.postnl.nl divertissementsouvenirs.stores.shop.cafr.ebay.ca doorzenden.postnl.nl downloads.polkcountyiowa.gov easybanking.bnpparibasfortis.be