SSL Check WHOIS
Dashboard / Security Report

meegle.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.

meegle.com: SSL/TLS grade A+ (HTTPS Monitor)meegle.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+ 2.17.196.11 IPv4 WHOIS › A+ 2.17.196.17 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-18 15:35 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
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 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)
meegle.com301 → https://meegle.com/ → … → https://www.meegle.com/ → 200 OK302 → https://www.meegle.com/ → 200 OK
www.meegle.com301 → https://www.meegle.com/ → 200 OK200 OK
  • http://meegle.com redirects to HTTPS.

DNS Records

As a public resolver answered for meegle.com. Looked up 2026-11-18 15:35 UTC · 1 day ago

TypeRecords
A
AAAA None
NS
ns1.bpldns.com ns2.bpldns.net
MX None
SPF None

Certificate Identity

Common Namemeegle.com
Alt Names *.meegle.com meegle.com
IssuerCN=GeoTrust TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Validity 2026-11-18 to 2027-06-04 (196 days remaining)
KeyECDSA 256 bits (sha256RSA)
Serial Number09DCD6F5405D5550999D3609F0FB1E8B
SHA256 Fingerprint 67dd207dd9bc27318b60ae08ee0cb2019666c0656eadc1cea9ab52b1de802b6e
Pin SHA256AB9KuDBB2oIbbWwGk24g2Wer+2ERvmkhmXruUpTkvTM=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://status.geotrust.com CRL: http://cdp.geotrust.com/GeoTrustTLSRSACAG1-4.crl
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 199 days (maximum 200 days for certificates issued then)
Chain Issues
• Contains anchor (root CA included in chain)

Trust Chain Architecture

End-Entity Certificate
CN=*.meegle.com (Issuer: CN=GeoTrust TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US)
Intermediate CA
CN=GeoTrust TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US)
Root Certificate
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US)

TLS History & Relations

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

Certificates served

Certificate (SHA-256)IssuerValidServed
67dd207dd9bc2731… current GeoTrust TLS RSA CA G12026-11-18 → 2027-06-042026-11-18

Addresses

AddressCertificateSeen
2.17.196.11 67dd207dd9bc2731… 2026-11-18
2.17.196.17 67dd207dd9bc2731… 2026-11-18

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-18 15:35A+TLS 1.3 67dd207dd9bc2731… 2.17.196.11, 2.17.196.17

Other hosts seen on the same addresses