SSL Check WHOIS
Dashboard / Security Report

dotomi.com

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
B 159.127.40.136 IPv4 WHOIS › B 159.127.43.8 IPv4 WHOIS ›
B

Adequate Protection

Overall Rating
Assessed 2026-11-17 19:26 UTC

Grade Breakdown

Protocol Support 50%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Grade capped at B: server supports obsolete TLS 1.0/1.1.

Security Vulnerabilities Detected

  • •Obsolete TLS versions (1.0/1.1) supported.
  • •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_ECDHE_RSA_WITH_AES_256_CBC_SHA384

Protocol Details

Connection
ALPN http/1.1
SNI Required No
Supported Named Groups secp256r1 (inferred)
Post-Quantum Key Exchange No (no hybrid ML-KEM group such as X25519MLKEM768)
HTTP/3 (QUIC) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Downgrade Prevention Yes (TLS_FALLBACK_SCSV)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret No
OCSP Stapling No
HSTS Unknown (the HTTPS request to this IP failed)
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.2
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA0x002FRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA2560x003DRSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA2560x003CRSANo FS128Weak
TLS_RSA_WITH_AES_256_GCM_SHA3840x009DRSANo FS256Weak
TLS_RSA_WITH_AES_128_GCM_SHA2560x009CRSANo FS128Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
Chrome 80 / Win 10TLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
Firefox 115 / Win 10TLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
iOS 17 / SafariTLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
macOS 14 / SafariTLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
Android 14TLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
Chrome 69 / Win 7TLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
Chrome 49 / XP SP3TLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
IE 11 / Win 10TLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
IE 11 / Win 7TLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
Android 9.0TLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
Android 7.0TLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
Android 5.0TLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
Android 4.4.2TLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
Java 11TLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
Java 8u121TLS 1.2TLS_RSA_WITH_AES_256_CBC_SHASuccess
Android 4.0.4TLS 1.0TLS_RSA_WITH_AES_256_CBC_SHASuccess
Android 4.1.1TLS 1.0TLS_RSA_WITH_AES_256_CBC_SHASuccess
Baidu Jan 2015TLS 1.0TLS_RSA_WITH_AES_256_CBC_SHASuccess
Java 6TLS 1.0TLS_RSA_WITH_AES_256_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)
dotomi.com302 → https://dotomi.com/ → … → https://www.epsilon.com/us → 200 OK302 → https://www.epsilon.com/us → 200 OK
www.dotomi.com302 → http://www.conversantmedia.com/ → … → https://www.epsilon.com/us → 200 OK503 Service Unavailable · certificate does not cover this name
  • http://dotomi.com redirects to HTTPS.
  • https://dotomi.com forwards visitors to www.epsilon.com, a different site. View its report ›
  • www.dotomi.com serves a certificate that does not cover its name: browsers show a security warning there.

DNS Records

As a public resolver answered for dotomi.com. Looked up 2026-11-17 19:26 UTC · today

TypeRecords
A
AAAA None
NS
asia9.akam.net eur2.akam.net eur3.akam.net eur7.akam.net ns1-100.akam.net ns1-27.akam.net use4.akam.net usw1.akam.net
MX
0 dotomi-com.mail.protection.outlook.com
SPF
v=spf1 ip4:69.8.121.70 ip4:69.8.121.71 include:valueclick.com ~all

Certificate Identity

Common Namedotomi.com
Alt Names *.dotomi.com dotomi.com
IssuerCN=GlobalSign GCC R46 OV TLS CA 2025, O=GlobalSign nv-sa, C=BE
Validity 2026-08-31 to 2027-03-18 (121 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number733697FE804F99FDDC9F097B
SHA256 Fingerprint e6c40629d5e073598fed9454ccd06b8d1cff76ce897ae4ac9aaf148d45fbfdaa
Pin SHA256p+Sip1dmOKsaf5soMPLC1hoYWPUCVL9IwcZOBZ5DhA8=

Certificate Properties

Type OV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.globalsign.com/gsgccr46ovtlsca2025 CRL: http://crl.globalsign.com/gsgccr46ovtlsca2025.crl
DNS CAA Yes (configured) 0 issuewild "digicert.com" 0 issue "amazontrust.com" 0 issuewild "globalsign.com" 0 issue "amazonaws.com" 0 issue "digicert.com" 0 issue "globalsign.com" 0 issue "amazon.com" 0 issue "letsencrypt.org" 0 issue "awstrust.com" 0 issuewild "amazon.com"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 199 days (maximum 200 days for certificates issued then)
Chain Issues
• Contains anchor (root CA included in chain)

Trust Chain Architecture

End-Entity Certificate
CN=*.dotomi.com, O=Conversant LLC, L=Westlake Village, S=California, C=US (Issuer: CN=GlobalSign GCC R46 OV TLS CA 2025, O=GlobalSign nv-sa, C=BE)
Intermediate CA
CN=GlobalSign GCC R46 OV TLS CA 2025, O=GlobalSign nv-sa, C=BE (Issuer: CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE)
Root Certificate
CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE (Issuer: CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE)

TLS History & Relations

Everything our scans have seen for dotomi.com, first seen 2026-11-17; current certificate since 2026-11-17.

Certificates served

Certificate (SHA-256)IssuerValidServed
e6c40629d5e07359… current GlobalSign GCC R46 OV TLS CA 20252026-08-31 → 2027-03-182026-11-17

Addresses

AddressCertificateSeen
159.127.40.136 e6c40629d5e07359… 2026-11-17
159.127.43.8 e6c40629d5e07359… 2026-11-17

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-17 19:26BTLS 1.2 e6c40629d5e07359… 159.127.40.136, 159.127.43.8