01
What it wanted
The crosshairs: what the page was trying to get you to do. Where the "click here" went, what the form was asking for, what the point of the page was. A screenshot shows you a page. This says what it wanted.
In development
See where a link goes without going there
ScopedURL renders a page as a still image and hands you the image instead of the page. Nothing loads on your device, nothing runs, and nothing knows you looked.
A picture of the page, not the page
The page is opened somewhere else, photographed, and the photograph is what reaches you.
That is the whole of the safety argument, and it is a structural one rather than a detection one. There is no list of bad scripts to keep current, because no script reaches the device either way. ScopedURL collects and shares no metadata about what you scoped.
What comes back with it
02
What it runs
The scripts the page would have executed, how many and of what kind, none of which ran, because nothing was fetched to your device.
03
Where it goes
Every link on the page and every redirect it passes through, so you can see where it was sending you before you find out by arriving.
Without leaving what you were reading
The case it is built for: you are part way through an article and there is a link in it you do not trust. Long-press, share it to ScopedURL, look at what comes back, and open it from there if you want to. You never lose your place, and you never open something to find out what it was.
Whether to open it stays your decision. ScopedURL shows you what is there and does not decide for you, which is the same position Vigil takes.
Where it stands
Specified, not built. It is the second of Vigilcode's two products, and the capability can come to Vigil as a feature once it exists.
There are no app store listings yet, and there will not be links to any until there are.