What the website check does

If “LynbroSiteCheck” shows up in your server log, someone typed your address into the check on this site. Here is exactly what we request, what we keep, and who runs it.

The user agent in your log

The check identifies itself like this:

Mozilla/5.0 (compatible; LynbroSiteCheck/<version>; +<address of this page>)

It is not a crawler: it follows no links and never returns on its own. Every visit means a person entered your address and pressed the button.

What your server receives

For one check, your web server sees at most this:

  1. The front page, fetched with GET. HTML only, no images, scripts, styles or fonts; at most 2 MB and 8 seconds.
  2. Up to five redirects. Each new address is checked again before we follow it.
  3. One request on http:// to see whether it sends visitors on to https://. If https:// doesn’t answer at all, we try the front page once on http:// instead.
  4. One or two TLS handshakes to read the certificate; the second only if the first fails, so the report can say why.

On top of that come lookups in public DNS: the domain’s IP addresses, MX, SPF, DMARC and a short list of common DKIM selectors such as selector1 and google. They go through our server’s own resolver, not your web server. We don’t log in, submit forms or probe for vulnerabilities.

Public addresses only

Before the first request we look up every address the domain points to. If any belongs to a private network, localhost or another reserved range, the check stops. Only http and https on ports 80 and 443 are accepted; raw IP addresses, credentials inside the address and internal host names are refused. The connection is pinned to the approved address, so the domain can’t switch halfway. Nobody can use the check to look inside a closed network.

Limits that spare the checked site

  • A repeat check of the same address in the same language within 15 minutes gets the stored report. Your server hears nothing.
  • One visitor can run 6 checks in 10 minutes and 30 a day. The tool as a whole runs at most 600 a day.
  • A hidden form field and a same-site check stop simple bots.

These are the current settings.

What we store

Each check adds one line to a log on our server:

  • the time
  • the host name of the checked site, for example example.dk, not the full address
  • the language the report was shown in
  • whether the check succeeded, failed or was answered from the stored report
  • how many items were marked Fix and Check, and how long the check took
  • the ids of the items marked Fix or Check, for example dmarc_missing
  • a salted hash of the visitor’s IP address. The address itself is not stored.

The log serves statistics and spotting abuse. Lines are deleted automatically after 180 days, the default. The report sits in the server’s temporary store for 15 minutes, then expires. The counters behind the limits use the same hash and expire after 10 minutes and a day.

Questionnaires and cookies

The questionnaires on the Accessibility Act and NIS2 are worked out in your browser; the answers are neither sent to us nor saved. Neither the check nor the questionnaires set cookies or store anything in your browser. If you write to us through the form, your details are used to answer you.

Who runs it

Best Choice, an IT company in Rødovre, Denmark (CVR 44079844), that helps small businesses with websites, e-mail and IT security. The check runs on open source WordPress plugins from Lynbro: Lynbro Site Check does the checking, the accessibility rules come from Lynbro Accessibility Checker, and the list of tracking scripts from Lynbro Cookie Consent.

What the check can’t do

It sees one page as the server sends it. It runs no JavaScript, so cookies and banners that scripts create later are invisible to it. DKIM keys can’t be listed, only guessed from well-known names, so “not found” does not mean “missing”. Automated testing finds only part of the accessibility problems: in a UK government study from 2017, the best tool found 40 % of 142 barriers. The report is technical guidance and does not decide whether a site complies with the law.

Was it your site?

Write to us through the form at the bottom. There is no list of sites that may not be checked; to avoid visits altogether, your server can refuse the LynbroSiteCheck user agent.

Questions from site owners

Is LynbroSiteCheck an attack?

No. It fetches less than a browser does, because images and scripts are skipped. It tries no passwords, ports or known holes.

Can you tell me who checked my site?

No. The check stores no names, e-mail addresses or IP addresses, only a hash of the IP address.

Why did several requests arrive in the same second?

The front page, any redirects and the http:// probe are one check: usually two or three log lines, seven at most.

How long do you keep anything about my site?

The log line is deleted after 180 days; the report expires after 15 minutes.

Will you contact me because my site was checked?

No. The check sends no e-mails, neither to the person checking nor to the site owner.

Fixed price, no commitment

Get it fixed

Tell us which website it is and what the check showed. A person answers with a fixed price before any work starts.

  • A fixed price before we start
  • An answer by e-mail, no calls
  • Your details are used only to answer you

Fields marked with * are required.

What should be fixed?