SSL Check WHOIS
Dashboard / Security Report

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

ns2.pch.net: SSL/TLS grade T (HTTPS Monitor)ns2.pch.netT
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
2602:fe55:5::5 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.

T

Status Unknown

Overall Rating
204.42.254.5 · WHOIS ›
Assessed 2026-11-21 02:49 UTC

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Certificate does not match the domain name.

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)
ns2.pch.net302 → https://ns2.pch.net/ → 200 OK200 OK · certificate does not cover this name
  • http://ns2.pch.net redirects to HTTPS.

DNS Records

As a public resolver answered for ns2.pch.net and its domain pch.net. Looked up 2026-11-21 02:49 UTC · today

TypeRecords
ns2.pch.net
A
AAAA
MX
10 mail.pch.net 90 mail2.pch.net
SPF None
pch.net
A
AAAA
NS
anyns.pch.net ns2.pch.net ns3.pch.net
MX
20 extmx.pch.net 30 secmx.pch.net
SPF
v=spf1 include:_spf.pch.net -all

Certificate Identity

Common Namens2.pch.net
Alt Names puck.nether.net
IssuerCN=YR1, O=Let's Encrypt, C=US
Validity 2026-10-06 to 2027-01-04 (44 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number05BC4EE80304FF0B25058345E44BA10D234C
SHA256 Fingerprint 2495e14d0b307eb40a7e13d4e34a3b2e71b81975fdb878bd5cd23833ce473159
Pin SHA256ZqhMuOU8p34zCzNXePZeD5RCaxRd7D9Krsg0BHUg250=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://yr1.c.lencr.org/77.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 No — certificate does not cover this host
Validity Period 90 days (maximum 200 days for certificates issued then)
Policy Warnings
• Certificate does not cover ns2.pch.net (name mismatch): browsers will show an error.
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 No
Supported Named Groups X25519MLKEM768 SecP256r1MLKEM768 SecP384r1MLKEM1024 x25519 secp256r1 x448 secp521r1 secp384r1 ffdhe2048 ffdhe3072 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, SecP256r1MLKEM768, SecP384r1MLKEM1024
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 (certificate has no OCSP responder)
HSTS Unknown (the HTTPS request to this IP failed)
HSTS Preloading N/A (HSTS not enabled)
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 (server-preferred order)
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_128_CCM_SHA2560x1304ECDHEFS128Secure
# TLS 1.2 (server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_RSA_WITH_AES_256_GCM_SHA3840x009DRSANo FS256Weak
TLS_RSA_WITH_AES_128_GCM_SHA2560x009CRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA2560x003DRSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA2560x003CRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA0x002FRSANo FS128Weak
TLS_DHE_RSA_WITH_AES_256_GCM_SHA3840x009FDHEFS256Secure
TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCAADHEFS256Secure
TLS_DHE_RSA_WITH_AES_128_GCM_SHA2560x009EDHEFS128Secure
TLS_DHE_RSA_WITH_AES_256_CBC_SHA2560x006BDHEFS256Weak
TLS_DHE_RSA_WITH_AES_128_CBC_SHA2560x0067DHEFS128Weak
TLS_DHE_RSA_WITH_AES_256_CBC_SHA0x0039DHEFS256Weak
TLS_DHE_RSA_WITH_AES_128_CBC_SHA0x0033DHEFS128Weak

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_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.4-- No
Android 4.1.1-- No
Baidu Jan 2015-- No
Java 6-- No

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

Trust Chain Architecture

End-Entity Certificate
CN=puck.nether.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 ns2.pch.net, first seen 2026-11-21; current certificate since 2026-11-21.

Certificates served

Certificate (SHA-256)IssuerValidServed
2495e14d0b307eb4… current YR12026-10-06 → 2027-01-042026-11-21

Addresses

AddressCertificateSeen
204.42.254.5 2495e14d0b307eb4… 2026-11-21

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-21 02:49TTLS 1.3 2495e14d0b307eb4… 204.42.254.5

Other domains on the same certificate

Other hosts seen on the same addresses