SSL Check WHOIS
Dashboard / Security Report

uptak.in

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+ 3.109.23.169 IPv4 WHOIS › A+ 35.154.130.169 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-17 23:18 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_128_GCM_SHA256

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups x25519 secp256r1 secp384r1 secp521r1 (server preference order)
Post-Quantum Key Exchange No (no hybrid ML-KEM group such as 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 Yes (RFC 7627)
OCSP Stapling No
HSTS Yes 182 days · 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_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak

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_RSA_WITH_AES_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
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)
uptak.in301 → https://www.uptak.in/ → 403 Forbidden301 → https://www.uptak.in/ → 403 Forbidden
www.uptak.in301 → https://www.uptak.in/ → 200 OK200 OK
  • http://uptak.in redirects to HTTPS.

DNS Records

As a public resolver answered for uptak.in. Looked up 2026-11-17 23:18 UTC · today

TypeRecords
A
AAAA None
NS
ns-1454.awsdns-53.org ns-150.awsdns-18.com ns-1866.awsdns-41.co.uk ns-815.awsdns-37.net
MX None
SPF None

Certificate Identity

Common Nameuptak.in
Alt Names uptak.in *.uptak.in
IssuerCN=Amazon RSA 2048 S22, O=Amazon, C=US
Validity 2026-11-14 to 2027-06-01 (195 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number44834ADF09A70637E55CAF4FDAC9C988
SHA256 Fingerprint 0660595c92ead3bb1252923737b24a0836999a1204a3c83db9f392fb6d7b9480
Pin SHA2566bHk7rb6rMnPz69JYzWLdCCQrqeYY9/2bpzhEG+dPew=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.r2s22.amazontrust.com CRL: http://crl.r2s22.amazontrust.com/73JwH.crl
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 198 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=uptak.in (Issuer: CN=Amazon RSA 2048 S22, O=Amazon, C=US)
Intermediate CA
CN=Amazon RSA 2048 S22, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)
Root Certificate
CN=Amazon Root CA 1, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)

TLS History & Relations

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

Certificates served

Certificate (SHA-256)IssuerValidServed
0660595c92ead3bb… current Amazon RSA 2048 S222026-11-14 → 2027-06-012026-11-17

Addresses

AddressCertificateSeen
3.109.23.169 0660595c92ead3bb… 2026-11-17
35.154.130.169 0660595c92ead3bb… 2026-11-17

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-17 23:18A+TLS 1.3 0660595c92ead3bb… 3.109.23.169, 35.154.130.169

Other hosts seen on the same addresses