SSL Check WHOIS
Dashboard / Security Report

a2bookmarks.com

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.

a2bookmarks.com: SSL/TLS grade B (HTTPS Monitor)a2bookmarks.comB
Overall grade based on: IPv4: 1 of 1 complete · IPv6: 1 of 1 complete
All 2 endpoints share identical configuration Select an IP for owner, ASN & location
B 207.211.214.145 IPv4 WHOIS › B 2400:52e0:1e07::1161:1 IPv6 WHOIS ›
B

Adequate Protection

Overall Rating
Assessed 2026-11-17 08:16 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).

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 secp384r1 (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 · 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
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA3840xC02CECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA2560xC02BECDHEFS128Secure
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA2560xCCA9ECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA3840xC024ECDHEFS256Weak
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA0xC00AECDHEFS256Weak
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA2560xC023ECDHEFS128Weak
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA0xC009ECDHEFS128Weak

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_ECDSA_WITH_AES_256_GCM_SHA384Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
Android 9.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
Android 7.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
Android 5.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
Android 4.4.2TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
Java 11TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
Java 8u121TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384Success
Android 4.0.4TLS 1.0TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHASuccess
Android 4.1.1TLS 1.0TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHASuccess
Baidu Jan 2015TLS 1.0TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHASuccess
Java 6TLS 1.0TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHASuccess

* 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)
a2bookmarks.com301 → https://a2bookmarks.com/ → 200 OK200 OK
www.a2bookmarks.com403 Forbidden (unencrypted)403 Forbidden · certificate does not cover this name
  • http://a2bookmarks.com redirects to HTTPS.
  • www.a2bookmarks.com serves a certificate that does not cover its name: browsers show a security warning there.

DNS Records

As a public resolver answered for a2bookmarks.com. Looked up 2026-11-17 08:16 UTC · 4 days ago

TypeRecords
A
AAAA
NS
coco.bunny.net kiki.bunny.net
MX
0 a2bookmarks.com 0 mail.a2bookmarks.com
SPF
v=spf1 include:zcsend.net ~all v=spf1 +ip4:103.159.65.46 +include:relay.mailchannels.net +include:zcsend.net ~all v=spf1 +a +mx +ip4:103.159.65.2 +ip4:103.159.65.46 include:relay.mailchannels.net ~all
More than one SPF policy: receivers treat this as an error and SPF fails (RFC 7208).

Certificate Identity

Common Namea2bookmarks.com
Alt Names a2bookmarks.com
IssuerCN=YE1, O=Let's Encrypt, C=US
Validity 2026-10-30 to 2027-01-28 (67 days remaining)
KeyECDSA 256 bits (sha384ECDSA)
Serial Number05FCE264DB11B5B557AFA5EF9D984312375C
SHA256 Fingerprint f3b7548a4f2f5eacc301954c801e0bca17550fdb0531bcea16e348069ffa6dcf
Pin SHA2567dQoUuFkPh95CaZ+SaGSs2xS/0RV/eNEcSIyAdrsLrU=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://ye1.c.lencr.org/93.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
• Contains anchor (root CA included in chain)

Trust Chain Architecture

End-Entity Certificate
CN=a2bookmarks.com (Issuer: CN=YE1, O=Let's Encrypt, C=US)
Intermediate CA
CN=YE1, O=Let's Encrypt, C=US (Issuer: CN=Root YE, O=ISRG, C=US)
Intermediate CA
CN=Root YE, O=ISRG, C=US (Issuer: CN=ISRG Root X2, O=Internet Security Research Group, C=US)
Root Certificate
CN=ISRG Root X2, O=Internet Security Research Group, C=US (Issuer: CN=ISRG Root X2, O=Internet Security Research Group, C=US)

TLS History & Relations

Everything our scans have seen for a2bookmarks.com, first seen 2026-11-17; current certificate since 2026-11-17.

Certificates served

Certificate (SHA-256)IssuerValidServed
f3b7548a4f2f5eac… current YE12026-10-30 → 2027-01-282026-11-17

Addresses

AddressCertificateSeen
207.211.214.145 f3b7548a4f2f5eac… 2026-11-17
2400:52e0:1e07::1161:1 f3b7548a4f2f5eac… 2026-11-17

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-17 08:16BTLS 1.3 f3b7548a4f2f5eac… 207.211.214.145

Other hosts seen on the same addresses