SSL Check WHOIS
Dashboard / Security Report

www.richmondfed.info

Overall grade based on: IPv4: 2 of 2 complete · IPv6: 0 of 2 complete, 2 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2a02:26f0:82::17c8:5611 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a02:26f0:82::17c8:5733 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 2 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 2.22.250.151 IPv4 WHOIS › A+ 2.22.250.195 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-10-31 18:32 UTC

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%

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 (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No (certificate has no OCSP responder)
HSTS Yes 1 year · includeSubDomains
HSTS Preloading Not preloadedSubmit →
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
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_128_CCM_SHA2560x1304ECDHEFS128Secure
# TLS 1.2
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
iOS 17 / SafariTLS 1.3TLS_CHACHA20_POLY1305_SHA256Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
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.

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)
www.richmondfed.info301 → https://www.richmondfed.info/ → … → https://www.richmondfed.org/ → 200 OK301 → https://www.richmondfed.org/ → 200 OK
richmondfed.info301 → http://www.richmondfed.org/ → … → https://www.richmondfed.org/ → 200 OKConnection refused
  • http://www.richmondfed.info redirects to HTTPS.
  • https://www.richmondfed.info forwards visitors to www.richmondfed.org, a different site. View its report ›
  • richmondfed.info has no working HTTPS (connection refused): visitors who type that name do not reach the HTTPS site.

Certificate Identity

Common Namewww.richmondfed.info
Alt Names cfosurvey.org www.cfosurvey.org www.richmondfed.biz www.richmondfed.com www.richmondfed.info www.richmondfed.name www.richmondfed.net www.richmondfed.org www.richmondfed.tv www.richmondfed.us www.richmondfed.ws
IssuerCN=YR2, O=Let's Encrypt, C=US
Validity 2026-10-07 to 2027-01-05 (49 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number06A2696D9F0FCD6189E4EBA710C9E040414C
SHA256 Fingerprint 54d3ff87d246273cc9326783c35562f48af6c8a16ac46690ba28c6d2b3fdd713
Pin SHA256M6Iz9tABHN9p0UEnWlVw0l6zOxwefqcRAvXHvZ9R8WM=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://yr2.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 Yes
Validity Period 90 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=www.richmondfed.org (Issuer: CN=YR2, O=Let's Encrypt, C=US)
Intermediate CA
CN=YR2, 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 www.richmondfed.info, first seen 2026-06-22; current certificate since 2026-10-31.

Certificates served

Certificate (SHA-256)IssuerValidServed
54d3ff87d246273c… current YR22026-10-07 → 2027-01-052026-10-31

Addresses

AddressCertificateSeen
2.22.250.151 54d3ff87d246273c… 2026-10-31
2.22.250.195 54d3ff87d246273c… 2026-10-31

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-10-31 18:32A+TLS 1.3 54d3ff87d246273c… 2.22.250.151, 2.22.250.195

Other domains on the same certificate

Other hosts seen on the same addresses