SSL Check WHOIS
Dashboard / Security Report

connectid.yahoo.com

Add this badge to your site

Shows this report's grade and links back to it. It is read from the stored report, never a new scan; a report older than 30 days also shows the month it was checked.

connectid.yahoo.com: SSL/TLS grade A+ (HTTPS Monitor)connectid.yahoo.comA+
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
A+ 13.248.158.7 IPv4 WHOIS › A+ 76.223.84.192 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-21 21:46 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 No
Supported Named Groups X25519MLKEM768 x25519 secp256r1 secp384r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768
HTTP/3 (QUIC) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Downgrade Prevention Yes (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No
HSTS No
HSTS Preloading N/A (HSTS not enabled)
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_ECDSA_WITH_AES_128_GCM_SHA2560xC02BECDHEFS128Secure
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA3840xC02CECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA2560xCCA9ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA2560xC023ECDHEFS128Weak
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA3840xC024ECDHEFS256Weak
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA0xC009ECDHEFS128Weak
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA0xC00AECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_RSA_WITH_AES_128_GCM_SHA2560x009CRSANo FS128Weak
TLS_RSA_WITH_AES_256_GCM_SHA3840x009DRSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA2560x003CRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA2560x003DRSANo FS256Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak

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_ECDSA_WITH_AES_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_ECDSA_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)
connectid.yahoo.com301 → https://guce.yahoo.com/email/optout → 200 OK301 → https://guce.yahoo.com/email/optout → 200 OK
  • http://connectid.yahoo.com redirects to HTTPS.
  • https://connectid.yahoo.com forwards visitors to guce.yahoo.com, a different site. View its report ›

DNS Records

As a public resolver answered for connectid.yahoo.com and its domain yahoo.com. Looked up 2026-11-21 21:46 UTC · today

TypeRecords
connectid.yahoo.com
A
AAAA None
MX None
SPF None
yahoo.com
A
AAAA
NS
ns1.yahoo.com ns2.yahoo.com ns3.yahoo.com ns4.yahoo.com ns5.yahoo.com
MX
1 mta5.am0.yahoodns.net 1 mta6.am0.yahoodns.net 1 mta7.am0.yahoodns.net
SPF
v=spf1 redirect=_spf.mail.yahoo.com

Certificate Identity

Common Nameconnectid.yahoo.com
Alt Names src1.yahoo.com *.oath.com *.ouroath.com *.ouryahoo.com *.yahoo.com *.verizonmedia.com *.yahooinc.com *.yahoo.bg *.yahoo.ca *.yahoo.cn *.yahoo.co *.yahoo.co.in *.yahoo.co.nz *.yahoo.co.th *.yahoo.co.uk *.yahoo.com.ar *.yahoo.com.au *.yahoo.com.br *.yahoo.com.cn *.yahoo.com.hk *.yahoo.com.mx *.yahoo.com.ph *.yahoo.com.sg *.yahoo.com.tw *.yahoo.com.vn *.yahoo.com.my *.yahoo.co.id *.yahoo.de *.yahoo.ee *.yahoo.es *.yahoo.fr *.yahoo.hk *.yahoo.hu *.yahoo.ie *.yahoo.in *.yahoo.it *.yahoo.ph *.yahoo.pt *.yahoo.sg *.brightroll.com *.maktoob.com *.yahooapis.com *.yahoomusic.com *.vzbuilders.com *.makers.com *.yahoosportsbook.com *.isp.yahoo.com *.notdonedocumentary.com *.notdonefilm.com *.yahoosports.com *.yahoofinance.com *.broman.vzbuilders.com *.knowledge.yahoo.com *.advertising.yahoo.com *.builtbygirls.com *.yahoo.net *.games.com scout.com *.scout.com *.yahoo.ai *.yahoo30.com
IssuerCN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
Validity 2026-11-05 to 2027-01-27 (67 days remaining)
KeyECDSA 256 bits (sha256RSA)
Serial Number07B9E392BCDA5D716BF7F4B5B2E5E3F6
SHA256 Fingerprint d16d88892ae019ee6b8e773495c54ca1e93c920745e1cf3a6240265a9e716a45
Pin SHA256OXj+7TM0Y20s/A8L7HUE/4wJ8oYbRhCjjt4gFnROY3E=

Certificate Properties

Type OV Organization Validated
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 Yes (configured) 0 issue "digicert.com" 0 issue "globalsign.com" 0 issue "sectigo.com" 0 iodef "mailto:[email protected]"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 84 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=src1.yahoo.com, O=Yahoo Holdings Inc., L=New York, S=New York, 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 connectid.yahoo.com, first seen 2026-11-02; current certificate since 2026-11-21.

Certificates served

Certificate (SHA-256)IssuerValidServed
d16d88892ae019ee… current DigiCert Global G2 TLS RSA SHA256 2020 CA12026-11-05 → 2027-01-272026-11-21

Addresses

AddressCertificateSeen
13.248.158.7 d16d88892ae019ee… 2026-11-21
76.223.84.192 d16d88892ae019ee… 2026-11-21

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-21 21:46A+TLS 1.3 d16d88892ae019ee… 13.248.158.7, 76.223.84.192

Other domains on the same certificate

Other hosts seen on the same addresses