SSL Check WHOIS
Dashboard / Security Report

netnames.net

Overall grade based on: IPv4: 0 of 1 complete, 1 unreachable · IPv6: none

No HTTPS on netnames.net

Port 443 refuses connections on its IPv4 address: no HTTPS server is running.

204.74.99.103 IPv4 · Port 443 refused the connection: nothing is listening for HTTPS.
Checked 2026-11-17 15:34 UTC

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)
netnames.net301 → https://www.cscdbs.com/ → 200 OKConnection refused
www.netnames.net301 → https://www.cscdbs.com/ → 200 OKConnection refused
  • http://netnames.net redirects to HTTPS.
  • www.netnames.net has no working HTTPS either (connection refused).

DNS Records

As a public resolver answered for netnames.net. Looked up 2026-11-17 15:34 UTC · today

TypeRecords
A
AAAA None
NS
udns1.cscudns.com udns2.cscudns.org
MX
10 mxa-0015fd02.gslb.pphosted.com 10 mxb-0015fd02.gslb.pphosted.com
SPF
v=spf1 ip4:165.160.33.34 ip4:185.26.230.64/26 ip4:185.26.229.213/32 ip4:185.26.229.3/32 ip4:185.26.229.7/32 ip4:194.30.189.0/24 ip4:185.26.228.86/32 ip4:185.26.228.94/32 ip4:165.160.32.0/24 include:spf-0015fd02.pphosted.com include:customers.clickdimensions.com include:_spf.salesforce.com include:spf.mandrillapp.com -all

TLS History & Relations

Everything our scans have seen for netnames.net, first seen 2026-11-17.

Addresses

AddressCertificateSeen
204.74.99.103 no TLS 2026-11-17

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-17 15:34No HTTPS— 204.74.99.103

Other hosts seen on the same addresses