SSL Check WHOIS
Dashboard / Security Report

www.bbg.gov

Overall grade based on: IPv4: 1 of 1 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:2b80:994::a49 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a02:26f0:2b80:9a7::a49 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
23.206.64.90 · WHOIS ›
Assessed 2026-11-06 06:47 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.
  • •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)
www.bbg.gov301 → https://www.bbg.gov/ → … → https://www.usagm.gov/ → 200 OK301 → http://www.usagm.gov/ → … → https://www.usagm.gov/ → 200 OK
bbg.gov301 → https://bbg.gov/ → … → https://www.usagm.gov/ → 200 OK301 → http://www.usagm.gov/ → … → https://www.usagm.gov/ → 200 OK
  • http://www.bbg.gov redirects to HTTPS.
  • https://www.bbg.gov forwards visitors to www.usagm.gov, a different site. View its report ›

DNS Records

As a public resolver answered for www.bbg.gov. Looked up 2026-11-06 06:47 UTC · 11 days ago

TypeRecords
A
AAAA
NS of bbg.gov
eur6.akam.net ns1-227.akam.net ns1-63.akam.net use5.akam.net use9.akam.net usw2.akam.net
MX None
SPF None

Certificate Identity

Common Namewww.bbg.gov
Alt Names 2016.bbg.gov 2017.bbg.gov annualreport2014.bbg.gov bbg.gov dev.ibab.gov direct.usagm.gov direct.voa24.news direct.vozdeamerica.com feeds.voanews.com ibab.gov ibb.gov names.voa.gov notebook.bbg.gov tv.voa24.news usagm.gov voa.com voa.gov voa24.news www.bbg.gov www.direct.usagm.gov www.ibab.gov www.ibb.gov www.usagm.gov www.voa.com www.voa24.news
IssuerCN=YR2, O=Let's Encrypt, C=US
Validity 2026-10-06 to 2027-01-04 (47 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number06F6D967DFD99A1701908183682D1F4DFD00
SHA256 Fingerprint 923a2ff54d28e57557d6cfe8ebc25e4a8f94c32eff5f9a69ef28e29fb89e0428
Pin SHA256mRgpWjMravYUCLoSPhXeAxAPCoJ3QJCssBgZWte8CYw=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://yr2.c.lencr.org/1.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_AES_256_GCM_SHA384

Protocol Details

Connection
ALPN http/1.1
SNI Required No
Supported Named Groups X25519MLKEM768 x25519 secp256r1 (server preference order)
Post-Quantum Key Exchange Yes 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 Yes (RFC 7627)
OCSP Stapling No (certificate has no OCSP responder)
HSTS Yes 1 year · includeSubDomains · 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.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_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
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

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.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=www.usagm.gov (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.bbg.gov, first seen 2026-08-02; current certificate since 2026-11-06.

Certificates served

Certificate (SHA-256)IssuerValidServed
923a2ff54d28e575… current YR22026-10-06 → 2027-01-042026-11-06

Addresses

AddressCertificateSeen
23.206.64.90 923a2ff54d28e575… 2026-11-06

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-06 06:47BTLS 1.3 923a2ff54d28e575… 23.206.64.90

Other domains on the same certificate

Other hosts seen on the same addresses