A commercial register has never heard of nordfracht.example. It knows Nordfracht Logistik GmbH, Hamburg, HRB 118 402. The bridge between the two is the legal notice, and it is why research has to run in two waves.
The question a register cannot answer
Sales tools start from a domain because that is what a rep has: a website, an email signature, a line in a spreadsheet. Registers start from a legal entity, because that is what the law creates. The German commercial register is keyed by court and HRB number, the global legal-entity register by LEI, the EU VAT system by VAT ID. None of them has a column for a domain.
So the obvious approach, searching a register by the name on the website, is a fuzzy search. A search for a common trading name in a large city returns several entities, some dormant, some unrelated, some the holding company of the one you meant. Pick the wrong row and every downstream fact, from headcount to managing director, belongs to a stranger.
The legal notice is the bridge
Companies trading in Germany, Austria and Switzerland are required to publish an Impressum, a legal notice, on their website. By law it states the legal name, the legal form, the registered address, the register court and number, and the VAT ID where one exists. It is the one place on a domain where a company is obliged to tell you exactly who it is in the vocabulary a register understands.
That is why Caicle's first wave reads everything reachable from the domain itself: the legal notice, the website, the public job board, the technology fingerprint, the mail platform, the domain registration record and the Wayback history. The purpose of the wave is not to fill the dossier. It is to establish identifiers.
Two waves, in that order
The second wave feeds those identifiers to the registers. An HRB number with a court is an exact lookup in the commercial register. A VAT ID is an exact confirmation in the EU VIES system. A company name plus a city is a strong query to the global legal-entity register, and where Wikidata already holds a verified LEI for the company, the query becomes one exact hit with parent and child entities attached.
The order matters because the second wave is only as good as the identifiers the first wave found. Running them in parallel would mean asking the register a fuzzy question while the answer sat in the legal notice, unread.
A verified LEI turns a fuzzy name search into one exact hit. That is the difference between attaching the right parent company and attaching a stranger's.
What happens when the bridge is missing
Not every domain has a legal notice, and not every legal notice is complete. A UK company is not obliged to publish one; a Swiss sole trader may only list a name. In those cases the second wave has weaker identifiers, and Caicle's precedence rules take over: a register-established value beats one from the legal notice, which beats Wikidata, which beats the company's own website copy.
Where the name match is ambiguous, Caicle refuses rather than guesses. A single-word name without a country is refused outright. The dossier records the field as not established, and the relationship graph does not attach a parent it cannot defend. A blank you can see is worth more than a plausible value you cannot source.
Why this matters for the first call
When the identifiers are right, everything downstream becomes quotable. The rep can say that the commercial register lists a managing director appointed this spring, that the VAT registration is confirmed, that the parent entity in the LEI register is the one in Vienna. Each of those sentences carries a source, a URL and a date in the dossier.
When the identifiers are wrong, the same sentences are confidently false, and the prospect will know it before the rep does. Two waves in the right order is how Caicle keeps the second case from happening.