urchin.com
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:c1d::63 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:c1d::69 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:c1d::6a 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:c1d::93 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 142.251.168.103 IPv4 WHOIS › B 142.251.168.104 IPv4 WHOIS › B 142.251.168.105 IPv4 WHOIS › B 142.251.168.106 IPv4 WHOIS › B 142.251.168.147 IPv4 WHOIS › B 142.251.168.99 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 | 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 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) |
|---|---|---|
| urchin.com | 301 → https://www.google.com/analytics/ → … → https://marketingplatform.google.com/about/analytics/ → 200 OK | 301 → https://www.google.com/analytics/ → … → https://marketingplatform.google.com/about/analytics/ → 200 OK |
| www.urchin.com | 301 → https://www.google.com/analytics/ → … → https://marketingplatform.google.com/about/analytics/ → 200 OK | 301 → https://www.google.com/analytics/ → … → https://marketingplatform.google.com/about/analytics/ → 200 OK |
- http://urchin.com redirects to HTTPS.
- https://urchin.com forwards visitors to www.google.com, a different site. View its report ›
DNS Records
As a public resolver answered for urchin.com. Looked up 2026-11-17 12:30 UTC · today
| Type | Records |
|---|---|
| A | |
| AAAA | |
| NS | ns1.google.com ns2.google.com ns3.google.com ns4.google.com |
| MX | 0 smtp.google.com |
| SPF | v=spf1 include:_spf.google.com ~all |
Certificate Identity
| Common Name | urchin.com |
| Alt Names | *.google-analytics.com region1.app-measurement.com app-measurement.com region1.att.app-measurement.com att.app-measurement.com region1.analytics.app-measurement.com analytics.app-measurement.com region1.app-analytics-services-att.com app-analytics-services-att.com region1.app-analytics-services.com app-analytics-services.com google-analytics.com region1.google-analytics.com ssl.google-analytics.com www.google-analytics.com region1.analytics.google.com googletagmanager.com www.googletagmanager.com urchin.com service.urchin.com fps.goog *.fps.goog googleoptimize.com www.googleoptimize.com |
| Issuer | CN=WE2, O=Google Trust Services, C=US |
| Validity | 2026-11-03 to 2027-01-26 (69 days remaining) |
| Key | ECDSA 256 bits (sha256ECDSA) |
| Serial Number | 3B367D1BB8E3344E0972C173CAB83DC7 |
| SHA256 Fingerprint | 51225e8ceac963eb903be2bd00ff472b27cef11e516e69120cbbe45c0ef92861 |
| Pin SHA256 | dFbE8xCcxRDHKDfuOrbH2WdpIKu6y5Q2KOtjGoYPbUc= |
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-analytics.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 urchin.com, first seen 2026-09-07; current certificate since 2026-11-17.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 51225e8ceac963eb… current | WE2 | 2026-11-03 → 2027-01-26 | 2026-11-17 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 142.251.168.99 | 51225e8ceac963eb… | 2026-11-17 |
| 142.251.168.103 | 51225e8ceac963eb… | 2026-11-17 |
| 142.251.168.104 | 51225e8ceac963eb… | 2026-11-17 |
| 142.251.168.105 | 51225e8ceac963eb… | 2026-11-17 |
| 142.251.168.106 | 51225e8ceac963eb… | 2026-11-17 |
| 142.251.168.147 | 51225e8ceac963eb… | 2026-11-17 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-17 12:30 | B | TLS 1.3 | 51225e8ceac963eb… | 142.251.168.99, 142.251.168.103, 142.251.168.104, 142.251.168.105, 142.251.168.106, 142.251.168.147 |
Other domains on the same certificate
- app-measurement.com 6 names
- google-analytics.com 5 names *.google-analytics.com region1.google-analytics.com ssl.google-analytics.com www.google-analytics.com
- app-analytics-services-att.com 2 names
- app-analytics-services.com 2 names
- fps.goog 2 names *.fps.goog
- googleoptimize.com 2 names
- googletagmanager.com 2 names
- google.com 1 name