track.sephora.me
Overall grade based on: IPv4: 6 of 6 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:2b80:2f::215:8f45 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a02:26f0:2b80:2f::215:8f53 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 6 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 2.21.23.196 IPv4 WHOIS › A+ 2.21.23.198 IPv4 WHOIS › A+ 2.21.23.199 IPv4 WHOIS › A+ 2.21.23.210 IPv4 WHOIS › A+ 2.21.23.219 IPv4 WHOIS › A+ 2.21.23.251 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 | h2 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 182 days |
| 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) |
|---|---|---|
| track.sephora.me | 301 → https://track.sephora.me/ → 200 OK | 200 OK |
- http://track.sephora.me redirects to HTTPS.
DNS Records
As a public resolver answered for track.sephora.me and its domain sephora.me. Looked up 2026-11-06 23:00 UTC · 10 days ago
| Type | Records |
|---|---|
| track.sephora.me | |
| A | |
| AAAA | |
| MX | None |
| SPF | None |
| sephora.me | |
| A | |
| AAAA | |
| NS | a1-1.akam.net a18-66.akam.net a20-67.akam.net a26-64.akam.net a7-65.akam.net a9-66.akam.net |
| MX | 20 a.mx.domainoo.fr |
| SPF | v=spf1 -all |
Certificate Identity
| Common Name | track.sephora.me |
| Alt Names | apps.sephora.me cms.sephora.me comm.sephora.me img-product.sephora.me sephora.me track.sephora.me www.sephora.me |
| Issuer | CN=YR1, O=Let's Encrypt, C=US |
| Validity | 2026-10-16 to 2027-01-14 (57 days remaining) |
| Key | RSA 2048 bits (sha256RSA) |
| Serial Number | 05A6169B6ED722575BD713A4FB98CAF46E17 |
| SHA256 Fingerprint | a5333494ee0784c16ff2254890fc5c7f485124be0dd7cc9886150dfcb811f40c |
| Pin SHA256 | w7AD6Na/6Y7blw4kJZc8lPMO8K6E7skQF3SIh3GDBss= |
Certificate Properties
| Type | DV |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) CRL: http://yr1.c.lencr.org/24.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=sephora.me (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 track.sephora.me, first seen 2026-09-16; current certificate since 2026-11-06.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| a5333494ee0784c1… current | YR1 | 2026-10-16 → 2027-01-14 | 2026-11-06 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 2.21.23.196 | a5333494ee0784c1… | 2026-11-06 |
| 2.21.23.198 | a5333494ee0784c1… | 2026-11-06 |
| 2.21.23.199 | a5333494ee0784c1… | 2026-11-06 |
| 2.21.23.210 | a5333494ee0784c1… | 2026-11-06 |
| 2.21.23.219 | a5333494ee0784c1… | 2026-11-06 |
| 2.21.23.251 | a5333494ee0784c1… | 2026-11-06 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-06 23:00 | A+ | TLS 1.3 | a5333494ee0784c1… | 2.21.23.196, 2.21.23.198, 2.21.23.199, 2.21.23.210, 2.21.23.219, 2.21.23.251 |
Other hosts seen on the same addresses
aaloans.myonlineaccount.co.uk anywhere.ebay.pl api.123-reg.co.uk apop-admin-int.postoffice.co.uk applyreferral.creation.co.uk assets.livekarriere.dk cart.123-reg.co.uk ebaycanada.com ebayindia.com events.fnac.be gov.sportsbet.com.au help2help.fondation.bnpparibas impact.interactivebrokers.hu impact.interactivebrokers.ie klm.aw klm.com.hk klm.gp manulinksit1.manulife.co.jp manutouch.com.sg newbalance.de profile-preprod-fidc.postoffice.co.uk rus.azadliq.mobi secure-payments.creation.co.uk sellercentre.ebay.ie synergy-uat.manulife.com.vn uat.mwa.com.my vi.ebaydesc.es www.azatliq.eu www.cheapoair.mx www.dailytelegraphdev.com.au