Skip to content

URL scanner

Paste a link to inspect where it really goes, how it is served and what the page tries to do. The fetcher refuses anything that resolves to a private, loopback or cloud metadata address.

Scan a URL Max 300 MB

Checks redirects, TLS, DNS, page structure and threat intelligence. Internal, loopback and cloud metadata addresses are always blocked.

HTTPS does not mean safe. A valid certificate only proves the connection is encrypted. Phishing sites routinely use free certificates.

Checks performed

  • Redirect chain, capped at five hops, each hop re-validated.
  • Final destination, resolved public IP and hostname reputation.
  • TLS certificate subject, issuer, validity and expiry.
  • DNS records (A, AAAA, MX, TXT, NS, CNAME) where available.
  • Password forms, cross-origin form actions and hidden iframes.
  • Obfuscated JavaScript, meta refreshes and mixed content.
  • Google Safe Browsing, URLhaus and PhishTank when configured.
  • RDAP registration age for recently created domains.
The report

What you can review after a URL scan

Destination

Original and final URL, domain, resolved addresses, HTTP status, redirect hops and the certificate chain summary.

Behaviour

Forms and where they submit, password fields, hidden iframes, external scripts, base-href hijacking and JavaScript obfuscation patterns.

Reputation

Threat-intelligence matches, domain age, per-vendor results and an overall risk assessment that separates confirmed findings from missing coverage.

Safe by design

How the fetcher is constrained

SSRF protection

Only HTTP and HTTPS on ports 80, 443, 8080 and 8443. Every resolved address must be globally routable; loopback, RFC1918, link-local, CGNAT, reserved and cloud metadata addresses are refused.

DNS rebinding protection

The validated IP is pinned for the connection, so a hostname cannot resolve publicly during validation and then privately when the request is sent. Redirect targets are validated again.

Bounded responses

Page bodies are capped at 512 KB and all requests have connect and read timeouts. A huge or slow page cannot hold a worker indefinitely.

No credentials in URLs

URLs containing embedded usernames or passwords are rejected, and the fetcher ignores proxy environment variables so requests cannot be routed through an unintended proxy.

Scanning a download link instead?

URL File downloads the file through the same protected fetcher, then runs the file pipeline.

Open URL File