A colleague sends you a screenshot. It shows your company’s internet address, a software name and a date. The message above it says, “Anyone can see our system!” Before deciding that someone has broken in, it helps to understand how that information could have been collected.
When you open a website, your browser sends a request to another system. The browser is a program; the server at the other end is a computer system running a service that can answer.
To reach that system across the internet, the program uses a network address, called an IP address. A human-friendly website name can lead to that address. The connection also specifies a number called a port, which helps direct it to the appropriate service. One system can offer different services through different ports. You do not usually see these numbers when opening an ordinary website. 15
An internet scanner automates making contact and recording responses. It can work through network addresses and service destinations rather than waiting for a link on someone’s homepage. A search service can then organise collected observations so people can look them up. The collecting program and the person later reading its results are not necessarily doing anything at the same time. This is why a system can appear in such a search even if the owner never submitted a web page to a conventional search engine. 11 15
Some internet search services look for computers and services rather than ordinary web articles. They record information returned when those services are contacted. Shodan, for example, describes collecting service “banners”: replies containing information such as a software description or a welcome message. Finding such a reply is not the same as logging into an account. 11
Looking at the entrance is not entering the building
Think of someone recording the signs visible at a building’s entrance. The signs can reveal that a business operates there and what kind of entrance it has. They do not establish that the observer opened a locked office or read the files inside. A scanner’s service record can likewise reveal useful information without proving an intrusion. 11
The analogy has limits. Internet scanners do more than read a sign from a distance: collecting information can involve making network connections and asking the service to respond. Censys describes protocol exchanges and requests for web pages, including additional requests used to recognise the service. These are the operator’s descriptions of its method, not measurements carried out for this article. 15
Follow a simple portal observation. The collector makes a connection to a reachable web service. The service replies with information about itself or supplies a page. The collector can record the address, the time, a returned software label and, for a protected connection, certificate information. If the page supplied is a login page, the result shows that the collector obtained that public page. It does not show that the collector supplied a correct password or opened the invoice view beyond it. A reply from the service is evidence of that reply, not of every action the service can perform. 11 15
Now change one detail in the example: the service returns a sensitive document directly, without requiring permission. That response would matter even if the collector never guessed a password. “No sign-in attempted” cannot make a confidential document public safely. Conversely, a password prompt visible from outside can be normal for a customer portal. To interpret the result, first establish what was returned, then compare it with what outsiders should be allowed to receive. The distinction is about the actual contents and intended access, not about whether the word “scanner” sounds alarming.
Censys says it does not try to get into a system by signing into an account. That does not mean its collection can never include content. For a messaging method used by connected devices, called MQTT, it documents possible samples of publicly broadcast messages that require no sign-in. The exact kind of service matters. Do not turn one operator’s description into a promise about every scanner. 15
For a business owner, the important question is what the particular result contains. A software description, a certificate and an openly returned message are different observations. None should be silently rewritten as “all customer data was downloaded.” Equally, genuinely public sensitive content should not be dismissed merely because no password was used to obtain it.
Four different questions hidden in one screenshot
First, was the service discovered? A record may show that a collector found a responding service at a particular address. Censys describes discovery relative to its earlier observations. Its first record is therefore not necessarily the moment the service was created. It is a fact about what the collector observed. 15
Second, what was reachable? A public login page may be exactly what the operator intended. An administration screen intended only for internal staff raises a different question. Visibility needs to be compared with the service’s purpose. That comparison cannot be settled by the mere existence of a search result.
Third, is there a weakness? A reported software name or version can be a useful clue, but the information returned by a service is not a complete inspection of its installed code, updates and configuration. Treat the label as something for the operator to confirm before concluding that a particular defect is present. 11
Fourth, did anyone exploit a weakness or obtain unauthorised access? That is the claim people usually mean by “hacked.” It needs evidence of the actual event. A banner alone does not show a successful login, changed records or stolen invoices. Keeping the questions separate helps you investigate the important issue rather than argue over an alarming headline. 11
Reading a record and making a new connection are different
If you look up information that a search service has already collected, you may not be contacting the supplier’s system at all. That is a passive lookup relative to the supplier, provided the lookup does not trigger a new scan. The earlier collection can still have involved active connections. Those two descriptions are compatible because they refer to different actions. 15
Opening the supplier’s website is different again: your browser makes direct requests. A technical assessment that tries several connection settings makes further requests. These activities should not all be described as “just looking at public records.” If you commission testing, agree what may be contacted and what the tester may do before it begins.
Time matters as much as method. The date you opened a search result is not necessarily the date the service was observed. Censys describes recurring collection and refresh, not a continuously current picture of every service. An old record can be useful history, but it should not quietly become a claim about today’s configuration. 15
A public certificate record is another kind of evidence. It can reveal a name without showing that the named website was reachable. Certificate Transparency logs and scanner connection records should therefore remain distinguishable. Two nearby timestamps do not establish that the scanner used the certificate record or that an attack followed. 8
Respond to the actual finding
A useful first response to our screenshot is to send it privately to the operator with the address, source and original observation time: “Does this belong to our service, and is this public access intended?” You do not need to accuse the supplier or dismiss the finding. You need an explanation of the specific system shown.
Keep the system straight. A supplier’s brochure website, customer login portal and software-to-software connection can run separately. A finding on the brochure site may reasonably prompt a question about maintenance, but it does not demonstrate a breach of invoice processing. The suggested connection between the two is a question, not an observed fact.
Hiding from a named search service is also not the same as fixing access. Censys describes blocking its collectors as an opt-out method and says this does not erase historical data. That addresses one collector. It does not establish that another observer cannot reach the service. For a private administrative function, the goal should be restricting unauthorised access generally. 14
If the operator needs to demonstrate who can view invoices, agree an authorised test environment with invented records. Do not try real invoice identifiers or other people’s credentials yourself. The result you want is a clear answer about the reported exposure, not a second incident created while investigating the first screenshot.
Sources
[8] Certificate Transparency — How CT Works