The first look
Before any test, Null looks at a site only as a browser or a search engine does: at most 5 requests to a site each time it looks, for its front page, /robots.txt, /sitemap.xml, /favicon.ico, /.well-known/security.txt and the scripts its front page loads. Each names us in its user agent: NullSquareRecon/1.0 (+https://nullsquare.net/recon).
What a test sends
A test is a look from outside with the tools of a security tester. It finds the sites and open services of the company, reads pages and files anyone can reach, and checks for known problems. It does not sign in, send forms or change anything. The company approves this before a test starts.
It connects only to the sites the company approved. It opens new connections to each address no faster than the speed the company approved, never more than 50 a second, and it sends nothing after its time is over or a person at the company stops it.
The tools of a test send their own user agents, so the sure way to know a test is the address it comes from.
What a test finds, we ask for again ourselves to prove it. These few requests are GET, HEAD and OPTIONS only, without a body, cookies or credentials, and each names us in its user agent: NullSquare-Security-Test/1.0 (+https://nullsquare.net/scanner).
The closer look
A company can also allow a closer look at its own sites, once, for up to 90 days. Once a day, and within the hour after a new site of theirs appears, it opens a TCP connection to each address the company runs its own sites on, on 28 common ports, and closes it at once. It sends nothing over the connection.
21 22 23 25 80 110 143 443 445 1433 2375 3000 3306 3389 5000 5432 5601 5900 6379 8000 8080 8443 8888 9000 9090 9200 11211 27017
It also asks each of those sites that answers on the web for two files a site must never serve, /.env and /.git/HEAD, and for one page that does not exist, to compare with. These are GET requests that name us in the user agent, as above.
It opens at most 4 connections a second to each address and at most 400 a day, and never looks at a site on a shared store, a name anyone could take over, or a site the company said not to test. It opens no connection to an address a hosting provider such as Cloudflare or Amazon CloudFront runs a site on, nor to the server of a site the company said not to test: a site a hosting provider runs is only asked for the two files.
Who asked for it
A test goes only to sites under a domain the company proved it owns, and only after a person at the company approved its terms: the sites, the speed and the time.
If a company proved only a subdomain, nothing else of its parent domain is tested.
Where it comes from
We publish the addresses our tests come from on this page before we test any customer's site.
If you did not expect it
If you run a site and see this traffic, but nobody at your company asked for a test, write to [email protected] with the time and the address the requests came from. We can stop that company's tests at once, then we look into it and reply.
A test only looks. A test reads what anyone on the internet can reach. It does not sign in, send forms or change anything.