Check seven screenshot endpoint controls.

Mark what your public source and tests can prove. The result identifies missing and uncertain gates, then builds a plain-text handoff in this browser.

Free local self-check · No account · No security score or certification · Updated July 20, 2026

0 of 7 answered Start with the input boundary.
0 of 7
1 · InputDoes the route accept only normalized absolute HTTP(S) URLs and reject URL credentials, unsafe ports, malformed hosts, and overlong input?

Confirm the behavior in code and negative tests, not only in UI validation or documentation.

2 · AddressAre IPv4, IPv6, and mapped addresses parsed and checked against loopback, private, link-local, metadata, and special-use ranges?

String checks for localhost or a few familiar IPv4 prefixes are not complete address validation.

3 · DNSDoes the route validate every DNS answer and control the address used when the browser actually connects?

A safe lookup followed by an uncontrolled second lookup leaves mixed-answer and rebinding exposure.

4 · NavigationIs the same destination policy enforced before every initial document, redirect, and frame connection?

Checking only the first URL or inspecting the final URL after navigation does not prevent the earlier network request.

5 · SubrequestsAre scripts, images, stylesheets, fonts, media, service workers, downloads, and background requests covered before connection?

A public top-level page can still make browser subrequests to an internal or metadata address.

6 · BoundsAre time, dimensions, document growth, response size, concurrency, browser isolation, and cleanup bounded?

Include failure cleanup and queue behavior; a navigation timeout alone does not bound the whole job.

7 · ApplicationDoes the application authorize the caller and keep secrets, full URLs, error detail, artifacts, and retention inside an explicit policy?

Network controls do not replace action authorization, safe logs, bounded storage, or a defined deletion path.

Answer all seven gates to build the handoff.