SSL Check WHOIS
adama.com has no HTTPS: HTTPS could not be reached on all 8 IPv4 addresses. The site is served on www.adama.com; this is its report. (adama.com checked 2026-08-14 10:06 UTC)
Dashboard / Security Report

www.adama.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.

www.adama.com: SSL/TLS grade A+ (HTTPS Monitor)www.adama.comA+
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 2 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 104.117.77.26 IPv4 WHOIS › A+ 104.117.77.42 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-18 19:33 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) 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 No
OCSP Stapling No (certificate has no OCSP responder)
HSTS Yes 2 years
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 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

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.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.adama.com403 Forbidden (unencrypted)403 Forbidden
adama.com301 → https://www.adama.com/ → 403 ForbiddenNo answer (timed out)
  • http://www.adama.com answers without redirecting to HTTPS: visitors who type the address without https:// get an unencrypted page.
  • adama.com has no working HTTPS (no answer): visitors who type that name do not reach the HTTPS site.

DNS Records

As a public resolver answered for www.adama.com and its domain adama.com. Looked up 2026-11-18 19:33 UTC · 4 days ago

TypeRecords
www.adama.com
A
AAAA None
MX None
SPF None
adama.com
A
AAAA None
NS
ns-1523.awsdns-62.org ns-1794.awsdns-32.co.uk ns-642.awsdns-16.net ns-67.awsdns-08.com
MX
10 adama-com.mail.protection.outlook.com
SPF
v=spf1 include:spf.protection.outlook.com ip4:72.32.141.120 ip6:2a01:1b0:7999:402::146 include:g2o-mailing.nl include:spf.emailsignatures365.com include:spf.mail-komplet.cz include:2550681.spf04.hubspotemail.net include:_spf-dc33.sapsf.eu ~all

Certificate Identity

Common Namewww.adama.com
Alt Names www.adama.com
IssuerCN=YE1, O=Let's Encrypt, C=US
Validity 2026-10-16 to 2027-01-14 (53 days remaining)
KeyECDSA 256 bits (sha384ECDSA)
Serial Number05C852789AB8413310B59E86E1B65E302497
SHA256 Fingerprint 2c4d441c48611493ad676dff78c2f2efcc4fce08c9b7129cc3d953a79a7745ad
Pin SHA256KeVBMvVdtjo7eAnvo6OY4299jnc/nABzAxtpgZVIFGY=

Certificate Properties

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

Certificates & Relations

The current state of www.adama.com as of our latest scan; certificate changed 2026-11-18.

Certificates served

Certificate (SHA-256)IssuerValid
2c4d441c48611493…YE12026-10-16 → 2027-01-14

Addresses

AddressAS
104.117.77.26 —
104.117.77.42 —

Other hosts on the same addresses