SSL Check WHOIS
Dashboard / Security Report

pch.net

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.

pch.net: SSL/TLS grade B (HTTPS Monitor)pch.netB
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
2620:0:872::231:147 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
206.220.231.147 · WHOIS ›
Assessed 2026-10-23 01:04 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)
pch.net301 → https://pch.net/ → … → https://www.pch.net/ → 200 OK301 → https://www.pch.net/ → 200 OK
www.pch.net301 → https://www.pch.net/ → 200 OK200 OK
  • http://pch.net redirects to HTTPS.

Certificate Identity

Common Namepch.net
Alt Names pch.net
IssuerCN=YR1, O=Let's Encrypt, C=US
Validity 2026-09-08 to 2026-12-07 (15 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number059DEEEA8C59E1F21008EF18DD1B95A8EB28
SHA256 Fingerprint b7c17f5b1be08b41e6d0c2f88a4c8e6c9f46445d983deff1a845faad1784f9c0
Pin SHA256anHe9nFiDogoj5bCYrWHC+ckAock02wtkFfRENuv5rQ=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://yr1.c.lencr.org/41.crl No OCSP responder — revocation is published via CRL only (as CA/B Forum rules now allow).
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 90 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_ECDHE_RSA_WITH_AES_256_GCM_SHA384

Protocol Details

Connection
ALPN No
SNI Required Yes
Supported Named Groups secp256r1 (inferred)
Post-Quantum Key Exchange No (no hybrid ML-KEM group such as X25519MLKEM768)
HTTP/3 (QUIC) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Downgrade Prevention Yes (TLS_FALLBACK_SCSV)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret No
OCSP Stapling No (certificate has no OCSP responder)
HSTS Yes 2 years · preload
HSTS Preloading Not preloadedSubmit →
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.2 (server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_DHE_RSA_WITH_AES_256_GCM_SHA3840x009FDHEFS256Secure
TLS_DHE_RSA_WITH_AES_128_GCM_SHA2560x009EDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_DHE_RSA_WITH_AES_256_CBC_SHA2560x006BDHEFS256Weak
TLS_DHE_RSA_WITH_AES_256_CBC_SHA0x0039DHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_DHE_RSA_WITH_AES_128_CBC_SHA0x0033DHEFS128Weak
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA0xC012ECDHEFS112Weak
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA0x0016DHEFS112Weak
TLS_RSA_WITH_AES_128_CBC_SHA0x002FRSANo FS128Weak
TLS_RSA_WITH_3DES_EDE_CBC_SHA0x000ARSANo FS112Weak
TLS_RSA_WITH_AES_256_GCM_SHA3840x009DRSANo FS256Weak
TLS_RSA_WITH_AES_256_CBC_SHA2560x003DRSANo FS256Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_DHE_RSA_WITH_AES_128_CBC_SHA2560x0067DHEFS128Weak
TLS_RSA_WITH_AES_128_GCM_SHA2560x009CRSANo FS128Weak
TLS_RSA_WITH_AES_128_CBC_SHA2560x003CRSANo FS128Weak

Handshake Simulation

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

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

Trust Chain Architecture

End-Entity Certificate
CN=pch.net (Issuer: CN=YR1, O=Let's Encrypt, C=US)
Intermediate CA
CN=YR1, O=Let's Encrypt, C=US (Issuer: CN=Root YR, O=ISRG, C=US)
Intermediate CA
CN=Root YR, O=ISRG, C=US (Issuer: CN=ISRG Root X1, O=Internet Security Research Group, C=US)
Root Certificate
CN=ISRG Root X1, O=Internet Security Research Group, C=US (Issuer: CN=ISRG Root X1, O=Internet Security Research Group, C=US)

TLS History & Relations

Everything our scans have seen for pch.net, first seen 2026-10-23; current certificate since 2026-10-23.

Certificates served

Certificate (SHA-256)IssuerValidServed
b7c17f5b1be08b41… current YR12026-09-08 → 2026-12-072026-10-23

Addresses

AddressCertificateSeen
206.220.231.147 b7c17f5b1be08b41… 2026-10-23

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-10-23 01:04BTLS 1.2 b7c17f5b1be08b41… 206.220.231.147

Other hosts seen on the same addresses