SSL Check WHOIS
Dashboard / Security Report

trust.adobe.com

IPv6: no public AAAA record — the domain is reachable over IPv4 only.
B

Adequate Protection

Overall Rating
185.34.190.18 · WHOIS ›
Assessed 2026-11-17 09:57 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).

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)
trust.adobe.com301 → https://www.adobe.com/trust.html → 200 OK301 → https://www.adobe.com/trust.html → 200 OK
  • http://trust.adobe.com redirects to HTTPS.
  • https://trust.adobe.com forwards visitors to www.adobe.com, a different site. View its report ›

DNS Records

As a public resolver answered for trust.adobe.com and its domain adobe.com. Looked up 2026-11-17 09:57 UTC · today

TypeRecords
trust.adobe.com
A
AAAA None
MX None
SPF None
adobe.com
A
AAAA
NS
a1-217.akam.net a10-64.akam.net a13-65.akam.net a26-66.akam.net a28-67.akam.net a7-64.akam.net
MX
1 adobe-com.mail.protection.outlook.com 2 adobe.mail.protection.outlook.com
SPF
v=spf1 exists:%{i}._i.%{d}._d.espf.agari.com include:%{d}.55.spf-protect.agari.com include:_spf.intacct.com IP4:172.193.27.96 -all

Certificate Identity

Common Nametrust.adobe.com
Alt Names redirect.adobe.com workfront.com translate.adobe.com cmo.com www.adobeexpress.com apps.enterprise.adobe.com www.echosign.adobe.com adobe.com ereg.adobe.com www.cmo.com www.creative.adobe.com campaign.adobe.com adobe.de digitalu.adobe.com cxo-roadmaps.adobe.com echosign.adobe.com www.acrobat.ai acrobat.ai genstudio.adobe.com cmo.adobe.com adobeexpress.com trust.adobe.com www.adobe-students.com www.adobe.de summit.adobe.com communities.adobe.com wikidocs.adobe.com
IssuerCN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
Validity 2026-11-03 to 2027-05-20 (184 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number05CE9AB4DE013B1307AE8526B991D68C
SHA256 Fingerprint f6e0209857c64c84c30145a6395c10e8bd7022965ad503422f94758a954d0954
Pin SHA256snaTvLACh7tSEFz0neQPJbSB7umjC4lBoWITB7pHzUc=

Certificate Properties

Type OV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Unknown (CRL could not be downloaded) OCSP: http://ocsp.digicert.com CRL: http://crl3.digicert.com/DigiCertGlobalG2TLSRSASHA2562020CA1-1.crl
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 199 days (maximum 200 days for certificates issued then)
Chain IssuesNone

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_128_GCM_SHA256

Protocol Details

Connection
ALPN No
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 Unknown
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
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 (server-preferred order)
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_RSA_WITH_AES_128_GCM_SHA2560x009CRSANo FS128Weak
TLS_RSA_WITH_AES_128_CBC_SHA0x002FRSANo FS128Weak
TLS_RSA_WITH_AES_128_CBC_SHA2560x003CRSANo FS128Weak
TLS_RSA_WITH_AES_256_GCM_SHA3840x009DRSANo FS256Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak
TLS_RSA_WITH_AES_256_CBC_SHA2560x003DRSANo FS256Weak
TLS_DHE_RSA_WITH_AES_128_GCM_SHA2560x009EDHEFS128Secure
TLS_DHE_RSA_WITH_AES_128_CBC_SHA0x0033DHEFS128Weak
TLS_DHE_RSA_WITH_AES_128_CBC_SHA2560x0067DHEFS128Weak
TLS_DHE_RSA_WITH_AES_256_GCM_SHA3840x009FDHEFS256Secure
TLS_DHE_RSA_WITH_AES_256_CBC_SHA0x0039DHEFS256Weak
TLS_DHE_RSA_WITH_AES_256_CBC_SHA2560x006BDHEFS256Weak

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Chrome 80 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Firefox 115 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
iOS 17 / SafariTLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
macOS 14 / SafariTLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 14TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Success
Android 4.0.4TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Success
Android 4.1.1TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Success
Baidu Jan 2015TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Success
Java 6TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Success

* Simulated based on server's supported protocols and cipher configuration.

Trust Chain Architecture

End-Entity Certificate
CN=redirect.adobe.com, O=Adobe Inc., L=San Jose, S=California, C=US (Issuer: CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US)
Intermediate CA
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US)
Root Certificate
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US)

TLS History & Relations

Everything our scans have seen for trust.adobe.com, first seen 2026-06-09; current certificate since 2026-11-17.

Certificates served

Certificate (SHA-256)IssuerValidServed
f6e0209857c64c84… current DigiCert Global G2 TLS RSA SHA256 2020 CA12026-11-03 → 2027-05-202026-11-17

Addresses

AddressCertificateSeen
185.34.190.18 f6e0209857c64c84… 2026-11-17

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-17 09:57BTLS 1.2 f6e0209857c64c84… 185.34.190.18

Other domains on the same certificate

Other hosts seen on the same addresses