SSL Check WHOIS
Dashboard / Security Report

bot.new

Overall grade based on: IPv4: 1 of 1 complete · IPv6: 0 of 1 complete, 1 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2001:4860:4802:32::1d 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.

B

Adequate Protection

Overall Rating
216.239.32.29 · WHOIS ›
Assessed 2026-10-24 05:46 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.
  • •Weak 3DES cipher supported (Sweet32).
  • •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)
bot.new301 → https://aistudio.google.com/vibe-code → 200 OK301 → https://aistudio.google.com/vibe-code → 200 OK
www.bot.new301 → https://aistudio.google.com/vibe-code → 200 OK301 → https://aistudio.google.com/vibe-code → 200 OK
  • http://bot.new redirects to HTTPS.
  • https://bot.new forwards visitors to aistudio.google.com, a different site. View its report ›

Certificate Identity

Common Namebot.new
Alt Names devsite-sni.developers.google.com docs.actifio.com d.actifio.com apigee.com *.apigee.com appdefensealliance.dev *.appdefensealliance.dev bazel.build *.bazel.build builders.google *.builders.google cel.dev *.cel.dev deepmind.google.com *.deepmind.google.com developer.nest.com developers.nest.com devsitetest.how *.devsitetest.how fuchsia.dev *.fuchsia.dev issues.fuchsia.dev *.issues.fuchsia.dev generativeai.google *.generativeai.google *.generativeai.google.com google.dev ai.google.dev www.ai.google.dev *.google.dev intrinsic.ai *.intrinsic.ai jibemobile.com *.jibemobile.com learn.mapsplatform.google.com *.learn.mapsplatform.google.com onboarding.off.goog *.onboarding.off.goog openthread.io *.openthread.io openweave.io *.openweave.io openxla.org *.openxla.org preview.source.android.com privacysandbox.google.com *.privacysandbox.google.com quantumai.google *.quantumai.google tensorflow.org *.tensorflow.org web.dev *.web.dev webrtc.org www.webrtc.org wing.com *.wing.com wing.dev *.wing.dev devsite.google *.devsite.google mediapipe.dev *.mediapipe.dev ai.dev *.ai.dev ai.studio *.ai.studio app.new *.app.new chat.new *.chat.new bot.new *.bot.new agent.new *.agent.new ai.app *.ai.app
IssuerCN=WE2, O=Google Trust Services, C=US
Validity 2026-09-28 to 2026-12-21 (34 days remaining)
KeyECDSA 256 bits (sha256ECDSA)
Serial Number009EA8C89706E8EBBB10ECFD62CE732824
SHA256 Fingerprint 19d2f011c653075055bd2173099c73e47323d4043b4c2a1b1ed9f5ba8b7186a6
Pin SHA256YrdHrEigCxsMjaF9GacFsLsnONdnaJeJ6yj0xO7UbOw=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://c.pki.goog/we2/xuzt3PU9F_w.crl No OCSP responder — revocation is published via CRL only (as CA/B Forum rules now allow).
DNS CAA Yes (configured) 0 issue "pki.goog"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 84 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_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 SecrecyYes (ECDHE / DHE)
Downgrade Prevention Yes (TLS_FALLBACK_SCSV)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No (certificate has no OCSP responder)
HSTS No
HSTS Preloading Preloaded
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.3 (server-preferred order)
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2 (server-preferred order)
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA2560xC02BECDHEFS128Secure
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA2560xCCA9ECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA3840xC02CECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA0xC009ECDHEFS128Weak
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA0xC00AECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
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_SHA0x002FRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak
TLS_RSA_WITH_3DES_EDE_CBC_SHA0x000ARSANo FS112Weak

Handshake Simulation

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

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

Trust Chain Architecture

End-Entity Certificate
CN=devsite-sni.developers.google.com (Issuer: CN=WE2, O=Google Trust Services, C=US)
Intermediate CA
CN=WE2, O=Google Trust Services, C=US (Issuer: CN=GTS Root R4, O=Google Trust Services LLC, C=US)
Root Certificate
CN=GTS Root R4, O=Google Trust Services LLC, C=US (Issuer: CN=GTS Root R4, O=Google Trust Services LLC, C=US)

TLS History & Relations

Everything our scans have seen for bot.new, first seen 2026-04-05; current certificate since 2026-10-24.

Certificates served

Certificate (SHA-256)IssuerValidServed
19d2f011c6530750… current WE22026-09-28 → 2026-12-212026-10-24

Addresses

AddressCertificateSeen
216.239.32.29 19d2f011c6530750… 2026-10-24

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-10-24 05:46BTLS 1.3 19d2f011c6530750… 216.239.32.29

Other domains on the same certificate

Other hosts seen on the same addresses