SSL Check WHOIS
Dashboard / Security Report

asus.click

IPv6: no public AAAA record — the domain is reachable over IPv4 only.
A+

Exceptional Security

Overall Rating
207.174.61.1 · WHOIS ›
Assessed 2026-11-03 00:20 UTC

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%

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)
asus.click301 → https://asus.click/ → … → https://www.asus.com/ → 200 OK302 → https://www.asus.com/ → 200 OK
www.asus.clickDoes not resolveDoes not resolve
  • http://asus.click redirects to HTTPS.
  • https://asus.click forwards visitors to www.asus.com, a different site. View its report ›
  • www.asus.click does not resolve: visitors who type it reach nothing.

Certificate Identity

Common Nameasus.click
Alt Names asus.click
IssuerCN=YE1, O=Let's Encrypt, C=US
Validity 2026-09-16 to 2026-12-15 (27 days remaining)
KeyECDSA 256 bits (sha384ECDSA)
Serial Number0514DFEE7B7D27742393549AFFB97393C3C4
SHA256 Fingerprint 3a3047677820210646cd9b75da1752e32867f671bb30e111438ac54ecf47bd40
Pin SHA256te7H5HqkqVJJSN6WpqO+geDPXlXYLf6gd+fKL+1Pplk=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://ye1.c.lencr.org/69.crl No OCSP responder — revocation is published via CRL only (as CA/B Forum rules now allow).
DNS CAA Yes (configured) 0 issue "letsencrypt.org" 0 issue "sectigo.com"
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_128_GCM_SHA256

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups X25519MLKEM768 SecP256r1MLKEM768 SecP384r1MLKEM1024 x25519 secp256r1 secp384r1 secp521r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, SecP256r1MLKEM768, SecP384r1MLKEM1024
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 Yes (RFC 7627)
OCSP Stapling No (certificate has no OCSP responder)
HSTS Unknown (the HTTPS request to this IP failed)
HSTS Preloading N/A (HSTS not enabled)
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 (server-preferred order)
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2 (server-preferred order)
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA2560xC02BECDHEFS128Secure
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA3840xC02CECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA2560xCCA9ECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA0xC009ECDHEFS128Weak
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA0xC00AECDHEFS256Weak

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_ECDSA_WITH_AES_128_GCM_SHA256 Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 9.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 7.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 5.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Android 4.4.2TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Java 11TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Success
Java 8u121TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 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.

Trust Chain Architecture

End-Entity Certificate
CN=asus.click (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 asus.click, first seen 2026-11-03; current certificate since 2026-11-03.

Certificates served

Certificate (SHA-256)IssuerValidServed
3a30476778202106… current YE12026-09-16 → 2026-12-152026-11-03

Addresses

AddressCertificateSeen
207.174.61.1 3a30476778202106… 2026-11-03

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-03 00:20A+TLS 1.3 3a30476778202106… 207.174.61.1

Other hosts seen on the same addresses