SSL Check WHOIS
Dashboard / Security Report

yahooapis.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.

yahooapis.com: SSL/TLS grade A+ (HTTPS Monitor)yahooapis.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-02 01:11 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 Yes
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 Yes 1 year
HSTS Preloading Not preloadedSubmit →
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)
yahooapis.com301 → http://developer.yahoo.com/ → … → https://consent.yahoo.com/v2/collectConsent → 200 OK301 → http://developer.yahoo.com/ → … → https://consent.yahoo.com/v2/collectConsent → 200 OK
www.yahooapis.comDoes not resolveDoes not resolve
  • http://yahooapis.com redirects to HTTPS.
  • https://yahooapis.com forwards visitors to developer.yahoo.com, a different site. View its report ›
  • www.yahooapis.com does not resolve: visitors who type it reach nothing.

Certificate Identity

Common Nameyahooapis.com
Alt Names src3.yahoo.com 5to1.com ahoo.com alfrasha.com alltheweb.com altavista.com au.tv.m.yahoo.com au.pfinance.yahoo.com dvd4arab.com majdah.com maktoob.com maktoobblog.com au.local.yahoo.com mybloglog.com overture.com rocketmail.com sport4ever.com travel4arab.com wretch.cc y7mail.com yahoo.ca yahoo.cn yahoo.co.in yahoo.co.th yahoo.com yahoo.com.ar 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.de yahoo.es yahoo.fr yahoo.in yahoo.it yahooapis.com yahoomail.com ycorpblog.com yimg.com ymail.com ysearchblog.com yahoo.bg yahoo.ie yahoo.hu www.whoknew.news.yahoo.com de.jahresrueckblick.yahoo.com espanol.finanzas.yahoo.net hk.blog.search.yahoo.com tw.security.yahoo.com yahoobillboard.com sandbox.jira.ouroath.com stage.jira.ouroath.com archive.jira.ouroath.com uk.makers.yahoo.com www.au.yahoo.com www.br.yahoo.com www.ca.yahoo.com www.de.yahoo.com www.es.yahoo.com www.espanol.yahoo.com www.fr.yahoo.com www.gr.yahoo.com www.hk.yahoo.com www.id.yahoo.com www.ie.yahoo.com www.buildseries.com makersconference.com cashay.com yahoosportsbook.com myyahoo.com yahoo.games yahoonews.com platinumpetpremonitions.com
IssuerCN=DigiCert Global G2 TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US
Validity 2026-10-13 to 2027-01-06 (46 days remaining)
KeyECDSA 256 bits (sha256RSA)
Serial Number06C3A30FC272EF2D13563B615DF4D359
SHA256 Fingerprint 9e7931d3382e3a7386c97d33997a0014571f63cce5aa09582f3ac89b93b62793
Pin SHA256Fy9LkQolfH6oHEOSgHAJj9oUQ7LYf/S0EmJb8j4rFC8=

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

Trust Chain Architecture

End-Entity Certificate
CN=src3.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 yahooapis.com, first seen 2026-08-03; current certificate since 2026-11-02.

Certificates served

Certificate (SHA-256)IssuerValidServed
9e7931d3382e3a73… current DigiCert Global G2 TLS RSA SHA256 2020 CA12026-10-13 → 2027-01-062026-11-02

Addresses

AddressCertificateSeen
13.248.158.7 9e7931d3382e3a73… 2026-11-02
76.223.84.192 9e7931d3382e3a73… 2026-11-02

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-02 01:11A+TLS 1.3 9e7931d3382e3a73… 13.248.158.7, 76.223.84.192

Other domains on the same certificate

Other hosts seen on the same addresses