SSL Check WHOIS
Dashboard / Security Report

ns2.dns-redirect.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.

ns2.dns-redirect.com: SSL/TLS grade T (HTTPS Monitor)ns2.dns-redirect.comT
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
2 different configurations detected across 2 endpoints Select an IP for owner, ASN & location
T 166.117.68.124 IPv4 WHOIS › T 76.223.91.20 IPv4 WHOIS ›
T

Status Unknown

Overall Rating
Assessed 2026-10-26 21:19 UTC

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Certificate is not trusted by any public store.

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 secp521r1 x448 ffdhe2048 ffdhe3072 (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 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
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_RSA_WITH_AES_256_GCM_SHA3840x009DRSANo FS256Weak
TLS_RSA_WITH_AES_128_GCM_SHA2560x009CRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA2560x003DRSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA2560x003CRSANo FS128Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak
TLS_RSA_WITH_AES_128_CBC_SHA0x002FRSANo FS128Weak

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_256_GCM_SHA384Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_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)
ns2.dns-redirect.com404 Not Found (unencrypted)404 Not Found · certificate does not cover this name
  • http://ns2.dns-redirect.com answers without redirecting to HTTPS: visitors who type the address without https:// get an unencrypted page.

Certificate Identity

Common Namens2.dns-redirect.com
IssuerCN=self-sign.com, OU=IT Department, O=Your Company, L=San Francisco, S=California, C=US
Validity 2026-10-23 to 2036-10-20 (3622 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number3617C96D2E1386ACCE27EE6E6E904F9FA836D176
SHA256 Fingerprint 86ba173c526a37d9ee5390c6adea4209c7c5e4ed1d1522eaee6d34442f9fd4e5
Pin SHA256JXSUCPIOQS/depZtL4HmbpL020JIJsUZj/+L4xoG560=

Certificate Properties

Type OV Organization Validated
Cert Transparency No
OCSP Must Staple No
Revocation N/A (self-signed)
DNS CAA No (missing)
Trusted By Not verified
Name Match No — certificate does not cover this host
Validity Period 3650 days (maximum 200 days for certificates issued then)
Policy Warnings
• Certificate does not cover ns2.dns-redirect.com (name mismatch): browsers will show an error.
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=self-sign.com, OU=IT Department, O=Your Company, L=San Francisco, S=California, C=US (Issuer: CN=self-sign.com, OU=IT Department, O=Your Company, L=San Francisco, S=California, C=US)

TLS History & Relations

Everything our scans have seen for ns2.dns-redirect.com, first seen 2026-10-26; current certificate since 2026-10-26.

Certificates served

Certificate (SHA-256)IssuerValidServed
10790e14784f09f3… current self-sign.com2026-10-19 → 2036-10-162026-10-26
86ba173c526a37d9… current self-sign.com2026-10-23 → 2036-10-202026-10-26

Addresses

AddressCertificateSeen
76.223.91.20 10790e14784f09f3… 2026-10-26
166.117.68.124 86ba173c526a37d9… 2026-10-26

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-10-26 21:19TTLS 1.3 10790e14784f09f3… 86ba173c526a37d9… 76.223.91.20, 166.117.68.124

Other hosts seen on the same addresses