vulnbeacon_TOOLS
← All tools

Web & TLS

TLS & certificate

Examine the trusted TLS connection to your hostname. This is a connection check, not an exhaustive cipher or protocol audit.

How to use TLS and certificateSteps, privacy & next steps

Check the trusted TLS connection and certificate served by your hostname.

Run this check

  1. Enter the intended public HTTPS URL.
  2. Confirm permission and provide an operating contact.
  3. Review hostname trust, expiration and the negotiated connection; repeat after a certificate change.

What you need

  • The HTTPS hostname whose certificate you want to inspect.

Your input & privacy

The tool opens a server-side TLS connection. It does not send a password, client certificate or application credentials.

Read the result

Connection details and renewal guidance describe the sampled endpoint. A successful handshake does not certify application security.

Keep in mind

  • One resolved address and negotiated connection are sampled, not every server, protocol or cipher.
  • An invalid certificate stops the check. No insecure retry, revocation audit or full certificate-chain assessment is performed.

Your inputs, explained.

JWTs, source snippets, passwords, CSP text, files, hashes and Base64 are processed in browser memory. This toolkit does not upload or save those inputs.

Website checks send the approved URL to this service and contact the target. DNS checks disclose the domain to Cloudflare DNS over HTTPS. Email-breach checks send the full address to Have I Been Pwned when configured and explicitly requested.

Server checks are transient and rate limited. This application does not write tool input or result logs; your hosting provider and contacted services may retain network metadata under their own policies. Exports are saved only when you choose to download them.

Use tools only for assets you own or have permission to assess. Private scans and their saved reports use the separate authenticated VulnBeacon application.