SSL Check WHOIS
Dashboard / Security Report

www.dc.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.dc.com: SSL/TLS grade A+ (HTTPS Monitor)www.dc.comA+
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 4 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 151.101.1.55 IPv4 WHOIS › A+ 151.101.129.55 IPv4 WHOIS › A+ 151.101.193.55 IPv4 WHOIS › A+ 151.101.65.55 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-22 01:56 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 X25519MLKEM768 x25519 secp256r1 secp384r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768
HTTP/3 (QUIC) Yes (advertised)
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 Yes
HSTS Yes 1 year
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_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure

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)
www.dc.com301 → https://www.dc.com/ → 200 OK200 OK
dc.com301 → https://dc.com/ → … → https://www.dc.com/ → 200 OK308 → https://www.dc.com/ → 200 OK
  • http://www.dc.com redirects to HTTPS.

DNS Records

As a public resolver answered for www.dc.com and its domain dc.com. Looked up 2026-11-22 01:56 UTC · today

TypeRecords
www.dc.com
A
AAAA None
MX None
SPF None
dc.com
A
AAAA None
NS
ns-1005.awsdns-61.net ns-1490.awsdns-58.org ns-1771.awsdns-29.co.uk ns-339.awsdns-42.com
MX
10 dc-com.mail.protection.outlook.com
SPF
v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all

Certificate Identity

Common Namewww.dc.com
Alt Names *.dc.com dc.com *.dccomics.com dccomics.com
IssuerCN=GlobalSign Atlas R46 DV TLS CA 2026 Q3, O=GlobalSign nv-sa, C=BE
Validity 2026-10-01 to 2027-04-18 (147 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number01735F79592C596E45E1585662155AB5
SHA256 Fingerprint 79548ce148fd5eeacc761d5aea2f9150dec2af9ffff0de8c622ecd0f3648e171
Pin SHA256dZiruUSeOXfgdS8S2CAC8/5OqzAkVyfXUkWorFmiL0A=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.globalsign.com/ca/gsatlasr46dvtlsca2026q3 CRL: http://crl.globalsign.com/ca/gsatlasr46dvtlsca2026q3.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 IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=*.dc.com (Issuer: CN=GlobalSign Atlas R46 DV TLS CA 2026 Q3, O=GlobalSign nv-sa, C=BE)
Intermediate CA
CN=GlobalSign Atlas R46 DV TLS CA 2026 Q3, O=GlobalSign nv-sa, C=BE (Issuer: CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE)
Root Certificate
CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE (Issuer: CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE)

TLS History & Relations

Everything our scans have seen for www.dc.com, first seen 2026-11-22; current certificate since 2026-11-22.

Certificates served

Certificate (SHA-256)IssuerValidServed
79548ce148fd5eea… current GlobalSign Atlas R46 DV TLS CA 2026 Q32026-10-01 → 2027-04-182026-11-22

Addresses

AddressCertificateSeen
151.101.1.55 79548ce148fd5eea… 2026-11-22
151.101.65.55 79548ce148fd5eea… 2026-11-22
151.101.129.55 79548ce148fd5eea… 2026-11-22
151.101.193.55 79548ce148fd5eea… 2026-11-22

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-22 01:56A+TLS 1.3 79548ce148fd5eea… 151.101.1.55, 151.101.65.55, 151.101.129.55, 151.101.193.55

Other domains on the same certificate

Other hosts seen on the same addresses