Every check / cors-reflects-any-origin
Will your server let any website read your customers' data?
On a domain you have proved is yours, we send one ordinary request carrying an Origin we made up, on our own domain, and read the headers that come back.
How it decides
The check speaks up when the server echoes that origin back, or accepts the null origin, and allows credentials with it.
Why it matters
A server that repeats back whatever origin it is told, with the visitor's login allowed, answers that way for anybody.
In more detail
A malicious page your customer has open in another tab can then read their account data from your site. An allowlist of the exact sites that need access closes it.
Who fixes it, and where it runs
- Who usually fixes it
- Whoever built your site
- Which plan runs it
- The Business plan
- Proof you own the site
- Needed. It asks your server for things an ordinary visitor never requests, so it waits until you prove the domain is yours.
More about this check
- Who it is about
- An intruder
- Listed under
- Instructions your site gives browsers
- The standards
- Its name in a report
cors-reflects-any-origin
See what the free scan finds
The free scan runs 62 checks on any address, and this is not one of them: it runs on the Business plan, once you prove the domain is yours.