www.schedule.meet
Overall grade based on: IPv4: 6 of 6 complete · IPv6: 0 of 4 complete, 4 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2a00:1450:400c:c21::64 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a00:1450:400c:c21::65 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a00:1450:400c:c21::8a IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a00:1450:400c:c21::8b 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.
All 6 endpoints share identical configuration Select an IP for owner, ASN & location
B 108.177.15.100 IPv4 WHOIS › B 108.177.15.101 IPv4 WHOIS › B 108.177.15.102 IPv4 WHOIS › B 108.177.15.113 IPv4 WHOIS › B 108.177.15.138 IPv4 WHOIS › B 108.177.15.139 IPv4 WHOIS › 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).
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 Secrecy | Yes (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 Compression | No (not supported by .NET TLS stack) |
| Heartbleed | Not tested |
Cipher Suite Analysis
| Cipher Suite | Hex | Key Exchange | FS | Bits | Strength |
|---|---|---|---|---|---|
| # TLS 1.3 | |||||
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| TLS_AES_256_GCM_SHA384 | 0x1302 | ECDHE | FS | 256 | Secure |
| TLS_CHACHA20_POLY1305_SHA256 | 0x1303 | ECDHE | FS | 256 | Secure |
| # TLS 1.2 | |||||
| TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | 0xC02B | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA9 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | 0xC02C | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA | 0xC009 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA | 0xC00A | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | 0xC02F | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA8 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | 0xC013 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | 0xC014 | ECDHE | FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_GCM_SHA256 | 0x009C | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_GCM_SHA384 | 0x009D | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_CBC_SHA | 0x002F | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_CBC_SHA | 0x0035 | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_3DES_EDE_CBC_SHA | 0x000A | RSA | No FS | 112 | Weak |
Handshake Simulation
| Client | Protocol | Cipher Suite | Result |
|---|---|---|---|
| Chrome 120 / Win 11 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Chrome 80 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Firefox 115 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| iOS 17 / Safari | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 | Success |
| macOS 14 / Safari | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Android 14 | TLS 1.3 | TLS_AES_128_GCM_SHA256 | Success |
| Chrome 69 / Win 7 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Chrome 49 / XP SP3 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| IE 11 / Win 10 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| IE 11 / Win 7 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 9.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 7.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 5.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 4.4.2 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Java 11 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Java 8u121 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 4.0.4 | TLS 1.0 | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA | Success |
| Android 4.1.1 | TLS 1.0 | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA | Success |
| Baidu Jan 2015 | TLS 1.0 | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA | Success |
| Java 6 | TLS 1.0 | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA | Success |
* 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.
| Host | http:// (port 80) | https:// (port 443) |
|---|---|---|
| www.schedule.meet | 404 Not Found (unencrypted) | 404 Not Found |
| schedule.meet | 302 → http://www.google.com/ → 200 OK | 302 → https://www.google.com/ → 200 OK |
- http://www.schedule.meet answers without redirecting to HTTPS: visitors who type the address without https:// get an unencrypted page.
Certificate Identity
Certificate Properties
| Type | DV |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) CRL: http://c.pki.goog/we2/64OUIVzpZV4.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 Issues | None |
Trust Chain Architecture
End-Entity Certificate
CN=google.meet (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 www.schedule.meet, first seen 2026-09-16; current certificate since 2026-11-01.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| b513a1654818240c… current | WE2 | 2026-10-07 → 2026-12-30 | 2026-11-01 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 108.177.15.100 | b513a1654818240c… | 2026-11-01 |
| 108.177.15.101 | b513a1654818240c… | 2026-11-01 |
| 108.177.15.102 | b513a1654818240c… | 2026-11-01 |
| 108.177.15.113 | b513a1654818240c… | 2026-11-01 |
| 108.177.15.138 | b513a1654818240c… | 2026-11-01 |
| 108.177.15.139 | b513a1654818240c… | 2026-11-01 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-01 19:44 | B | TLS 1.3 | b513a1654818240c… | 108.177.15.100, 108.177.15.101, 108.177.15.102, 108.177.15.113, 108.177.15.138, 108.177.15.139 |
Other domains on the same certificate
- addin.meet 2 names
- alphabet.meet 2 names
- apps.meet 2 names
- auth.meet 2 names
- buy.meet 2 names
- calico.meet 2 names
- capitalg.meet 2 names
- certified.meet 2 names
- deepmind.meet 2 names
- dial.meet 2 names
- d.meet 2 names
- download.meet 2 names
- events.meet 2 names
- get.meet 2 names
- gmail.meet 2 names
- go.meet 2 names
- google.meet 2 names
- gv.meet 2 names
- hardware.meet 2 names
- host.meet 2 names
- invite.meet 2 names
- join.meet 2 names
- lets.meet 2 names
- livestream.meet 2 names
- loon.meet 2 names
- makani.meet 2 names
- mobile.meet 2 names
- nest.meet 2 names
- new.meet 2 names
- partner.meet 2 names
- partners.meet 2 names
- present.meet 2 names
- quality.meet 2 names
- roadmap.meet 2 names
- room.meet 2 names
- rooms.meet 2 names
- setup.meet 2 names
- share.meet 2 names
- signup.meet 2 names
- tel.meet 2 names