Webshotter
Log in Sign up
Abuse

Report abuse

If one of our customers is pointing this service at your site, or an image from us is being used to deceive somebody, tell us. A person reads that address.

Email abuse@webshotter.com Read the acceptable use policy
Traffic from us
Our renderer is fetching your pages and you want it to stop, or to slow down. Send the user-agent line, the requesting IP addresses, the paths, and a time window with a timezone.
An image used to deceive
A webshot of a page made to look like something it is not — a fabricated receipt, statement, article or review. Send the image or a link to where it is being used.
Your brand impersonated
A page captured through us that imitates your sign-in screen or your communications. Send the URL that was rendered and anything showing where it was used.
Content behind your access control
A page of yours being rendered that should not be reachable without signing in. Tell us the URL and what should have stopped it.
Illegal material
Send it and we act immediately. Material involving children goes to the authorities, always, and the account is closed without notice.
A vulnerability, not abuse
That goes to security@ instead — the security page says what to include and what we promise back.

What happens after you send it

  1. We acknowledge within two working days, to the address you wrote from.
  2. We look for the renders in question in our own logs. A URL and a time window with a timezone is usually enough to find them; a user-agent and IP address makes it certain.
  3. We contact the customer, or — for anything involving illegal material, an active attack, or a credible threat to somebody's safety — we suspend first and ask afterwards.
  4. We tell you the outcome. We will not tell you who the customer is; that is between them, us, and anyone with the legal standing to ask.

Blocking us yourself

Be aware of what you are dealing with: our renderer is a real Chrome presenting the user-agent of the device the customer asked for, because the whole point of the product is that the page renders as it would for that device. It does not announce itself, and it does not currently read robots.txt. Blocking by user-agent will not work, and we would rather tell you that than let you believe it did.

What does work: blocking the requesting addresses at your edge — we will not route around a block — and telling us, which is faster, because we can stop the account rather than one of its routes to you. A self-identifying agent that honours robots.txt is on our list; until it ships, this paragraph stays as it is.

Court orders, law-enforcement requests and notices from a regulator go to legal@webshotter.com. Copyright complaints go there too — include the work, the URL, and a statement that you are authorised to act for the rights holder.

We would rather hear about it

Nothing on this page needs an account, and nothing about it is automated. It goes to people.

Create your account Read the docs