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 › 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 Secrecy | Yes (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 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_256_GCM_SHA384 | 0x1302 | ECDHE | FS | 256 | Secure |
| TLS_CHACHA20_POLY1305_SHA256 | 0x1303 | ECDHE | FS | 256 | Secure |
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| TLS_AES_128_CCM_SHA256 | 0x1304 | ECDHE | FS | 128 | Secure |
| # TLS 1.2 | |||||
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | ECDHE | FS | 256 | Secure |
| 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_CBC_SHA384 | 0xC028 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 | 0xC027 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | 0xC014 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | 0xC013 | ECDHE | FS | 128 | 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_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Chrome 49 / XP SP3 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 10 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 7 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 9.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 7.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 5.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 4.4.2 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 11 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 8u121 | TLS 1.2 | TLS_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.
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.richmondfed.info | 301 → https://www.richmondfed.info/ → … → https://www.richmondfed.org/ → 200 OK | 301 → https://www.richmondfed.org/ → 200 OK |
| richmondfed.info | 301 → http://www.richmondfed.org/ → … → https://www.richmondfed.org/ → 200 OK | Connection 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 Name | www.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 |
| Issuer | CN=YR2, O=Let's Encrypt, C=US |
| Validity | 2026-10-07 to 2027-01-05 (49 days remaining) |
| Key | RSA 2048 bits (sha256RSA) |
| Serial Number | 06A2696D9F0FCD6189E4EBA710C9E040414C |
| SHA256 Fingerprint | 54d3ff87d246273cc9326783c35562f48af6c8a16ac46690ba28c6d2b3fdd713 |
| Pin SHA256 | M6Iz9tABHN9p0UEnWlVw0l6zOxwefqcRAvXHvZ9R8WM= |
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 Issues | None |
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) | Issuer | Valid | Served |
|---|---|---|---|
| 54d3ff87d246273c… current | YR2 | 2026-10-07 → 2027-01-05 | 2026-10-31 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 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) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-10-31 18:32 | A+ | TLS 1.3 | 54d3ff87d246273c… | 2.22.250.151, 2.22.250.195 |
Other domains on the same certificate
- cfosurvey.org 2 names
- richmondfed.biz 1 name
- richmondfed.com 1 name
- richmondfed.name 1 name
- richmondfed.net 1 name
- richmondfed.org 1 name
- richmondfed.tv 1 name
- richmondfed.us 1 name
- richmondfed.ws 1 name
Other hosts seen on the same addresses
application.tsb.co.uk covid19info.biontech.de ertekbecsles.kh.hu majorel.mijnlogistiek.postnl.nl touch.kbcbrussels.be uk-india.britishcouncil.in www.britishcouncil.be www.britishcouncil.bh www.britishcouncil.ch www.britishcouncil.co.zw www.britishcouncil.hr www.britishcouncil.ly www.britishcouncil.org.au www.britishcouncil.si www.britishcouncil.tn www.fedeconjobs.org www.governo.it www.palazzochigi.eu www.palazzochigi.it www.richmondfed.net www.santanderprevi.com.br www.spheir.org.uk www-test.hankyu-travel.com