Domain to Company Resolver

One row per domain. The row joins RDAP (registrar and domain age), the website legal notice, a company-register match and a VAT check.

What does Domain to Company Resolver do?

Give it a list of domains (a lead list, a supplier site, a name that just showed up). For each domain it:

1. Reads RDAP the same way as Domain RDAP Lookup & Expiry Watch: registrar, created and expiry dates, domain age. Registrant and contact records are not stored.
2. Fetches the site and parses Impressum / Mentions légales / legal notice the same way as EU Impressum Lookup. Person names are not stored.
3. Looks up the legal name or register number in the same registers as EU Company Register Lookup.
4. Checks the VAT number with the same rules as EU TIN & VAT Validator. Personal numbers are format-checked only.

If the legal notice has no company fields, the register and VAT steps are skipped. That keeps a dead site cheap.

Why one run instead of calling the other Actors?

Actor.call() would start four more containers and add each Actor's own event price. A VAT check alone is $0.02 on the public validator, before RDAP ($0.0015), Impressum ($0.002) and the register ($0.003). This Actor imports those functions and runs them here. RUN_SUMMARY.chain is in-process and childActorCalls is 0. The other Actors are unchanged and are not billed.

Sitemap fetching is off unless you turn it on. A strong national register hit is not followed by a GLEIF name search.

What does a profile contain?

Field	Meaning
domain, registered, registrar	RDAP result. No registrant
createdAt, expiresAt, domainAgeDays	Registry dates. Some TLDs do not publish expiry
legalName, legalForm, registerType, registerNumber	From the legal notice, filled from the register when the match is strong
registerSource, registerStatus, lei, registerCountry	Register row
vatNumber, vatValid, vatExistence	vatValid is true only when the official source says the number exists
matchConfidence	0–100
warnings	See below

Warnings include unregistered, rdap_unsupported, rdap_unavailable, invalid_domain, no_register_match, name_mismatch, vat_invalid, vat_unverified, impressum_not_found, impressum_mismatch, impressum_fetch_error and impressum_robots.

Some shops (for example decathlon.fr) answer the homepage with HTTP 403 from a datacenter address. The row still keeps the RDAP result and sets impressum_fetch_error. The register and VAT steps stay skipped, because there is no legal-notice company to look up.

.io, .eu and the other suffixes the RDAP Actor marks unsupported are not sent to a registry. The legal notice is still read when you leave that option on.

A RDAP 404 sets registered to false. It does not mean the name is free to register.

How to run it

1. Paste domains under Domains. The default cap is 5 and the hard cap is 25.
2. Leave sitemap lookup off unless a first run reports impressum_not_found.
3. A Companies House key is optional and only used when the legal notice shows a UK company number.
4. Download the dataset. RUN_SUMMARY is in the key-value store.

An empty domain list finishes without charging and without any HTTP call.

How much does a domain cost?

Suggested pay-per-event price, not applied on this private Actor: $0.008 per domain-resolved.

That sits in the $0.005–$0.01 range from the pricing notes. $0.005 is enough when many domains have no legal notice (the register and VAT steps are skipped). $0.01 matches a full chain. $0.008 is the single event to set when the Actor is monetized.

The event is one domain that was actually queried, including a negative result. A string that is not a domain is stored and is not charged. Platform compute is separate. The default run is 256 MB.

Do not add the child Actor prices on top. Those Actors are not called.

Sources

RDAP, legal-notice pages, company registers and VIES are the sources already used by the four Actors above. No new data source was added.

Do not use this Actor to collect private individuals. A legal notice can name a sole trader; sole traders are dropped from the register step.