VulScoreWEBSITE SECURITY

Website security. Clearly measured.

SECURITY · SSL · PERFORMANCE

Check your website’s network

Check DNS resolution, TCP connectivity, and HTTPS certificate validation from this server.

Public domain names only. Tests ports 80 and 443 on one resolved address per IP family. URL paths are ignored. Maximum 15 seconds.

SAMPLE REPORT · ILLUSTRATIVE DATA

Network results

demo.example

04 Nov 2026 · 17:04 UTC

This report contains fabricated sample data. No external requests were made.

24 msSystem DNS lookup time
2Resolved addresses
2TCP connections established
1Validated TLS connections

Resolution uses this server’s configured DNS resolver. Connection timings are single observations, not ping latency. Only one IPv4 and one IPv6 address are sampled, and no HTTP request is sent. A timeout or refusal is inconclusive about availability elsewhere.

Resolved addresses

  • 192.0.2.10
  • 2001:db8::10
192.0.2.10 · port 80:Connected

What we observed

Sample TCP connection established.

TCP connection time: 32 ms. TLS handshake time is not included in this number.

What to review

Port 80 may be deliberately unavailable. Where HTTP is offered, use the security scanner to check its HTTPS redirect.

192.0.2.10 · port 443:Connected

What we observed

Sample TLS handshake and certificate validation succeeded.

TCP connection time: 35 ms. TLS handshake time is not included in this number.

What to review

Check HTTPS bindings, certificate hostname and trust, certificate renewal, firewall rules, and IPv6 routing when appropriate. A successful handshake is not a full TLS configuration audit.

2001:db8::10 · port 80:Inconclusive

What we observed

Sample IPv6 connection timed out.

What to review

Port 80 may be deliberately unavailable. Where HTTP is offered, use the security scanner to check its HTTPS redirect.

2001:db8::10 · port 443:Inconclusive

What we observed

Sample IPv6 connection timed out.

What to review

Check HTTPS bindings, certificate hostname and trust, certificate renewal, firewall rules, and IPv6 routing when appropriate. A successful handshake is not a full TLS configuration audit.

Reports are not stored. Use Print / Save as PDF to keep these results.

Public destinations

All resolved addresses are checked before connecting. A private or reserved address in the answer blocks the entire scan; connections use the exact validated IPs.

Bounded checks

Four connections maximum, with four-second per-connection limits. No arbitrary port ranges, ICMP ping, traceroute, or internal network scanning.

Certificate checks

TLS uses the submitted hostname and normal certificate chain validation. Revocation is not checked; missing intermediate certificates can cause validation to fail.