
Keep these fields in the source log
- Asset and authorised scope
- Source, observation type and timestamp
- Observed relationship and remaining hypotheses
Public research resources · FR / EN
Which public observations clarify a domain without contacting its target ? Practical method, external tools, source log and interpretation limits.
External services · no results hosted here · queries sent only when you click a provider link.



IIS performs no scan. At a third party, submitting a URL may trigger a visit and publication; never transmit tokens, private access or confidential files.
Entries draw on the providers’ portals or documentation. Each entry shows its latest review date. Check the provider for current access conditions, pricing and quotas.
All words must match. Word order, accents and case do not matter.
10 entries displayed
Consult public domain registration data.
Record the exact domain, lookup time and event labels returned by the registry. Distinguish the creation of the registration record from the first observed publication on the site.
Limit: Registrants may be redacted; a registrar or technical contact is not the website author.
Publisher reference · Record reviewed
Find domain names in certificates published in CT logs.
Limit: A certificate may be expired or unused; it does not establish current control.
Publisher reference · Record reviewed
Inspect public DNS records with the requested record type.
Limit: Resolution, cache and date matter; a shared IP does not establish a relationship between customers.
Record reviewed
Inspect indexed observations of Internet-facing assets and services.
Limit: Keep research within authorised scope; an old observation is not a current scan.
Record reviewed
Access an Internet infrastructure and certificate observation platform.
Limit: Access, platform and quotas evolve; confirm each observation timestamp.
Record reviewed
Search existing URL analyses and inspect their requests and screenshots.
In an existing result, record the scan time and distinguish the submitted URL from the final address displayed. A historical screenshot documents the observation at that time.
Limit: A new submission may become public and visit the target; avoid private URLs and tokens.
Publisher reference · Record reviewed
Inspect context for a domain, URL or known file hash.
Limit: Do not submit confidential files; verdicts may differ or be outdated.
Record reviewed
Examine IP prefixes, ASNs and routing history.
Record exact resource, historical interval, consulted dataset and observation time. Compare a route change with the reviewed period.
Limit: An ASN or route does not identify who is responsible for hosted content.
Record reviewed
Find network, exchange and interconnection-facility records.
Record ASN, record identifier, declared organisation and consultation date; corroborate decision-critical information.
Limit: User-maintained records do not prove current connectivity or website ownership.
Record reviewed
Consult IP-resource and ASN registration information.
Retain IP range, handle, organisation and contact role. Separate registered allocation, hosting provider and service operator.
Limit: The register does not precisely locate a device or attribute activity to a person.
Record reviewed
No matching catalogue entry. Try another term or reset the filters.






Reading technical evidence
An RDAP response pairs an event type with a date. Retain both fields together.
| Observed item | What it means |
|---|---|
| eventAction: registration | Registration event for the object; it does not date the website’s first publication. |
| eventAction: last changed | A change to the registered object; it does not prove a change of owner. |
| eventDate | Read the date with its UTC offset and the response consultation date. |
Record the exact domain and queried service. Corroborate the operator’s identity and publication history separately.
Read the original record
An RDAP response describes a registered object. Retain its type and the queried authority rather than labelling every field owner.
| Item | Record to retain | Limit |
|---|---|---|
| Object | objectClassName, handle and ldhName where present. | A domain object is not an IP-network object. |
| Entities | Declared roles and available identifiers. | Registrar, technical contact and registrant have different roles. |
| Events | eventAction with eventDate, plus consultation time. | An update does not prove that the website was sold. |
Reading exercise · fictional scenario
Two domains resolve to one shared-hosting IP address. No other matching identifier was found.
Before opening the explanation, separate what is observed from what is inferred. Identify the missing check that prevents the broader conclusion.

Both domains belong to the same organisation.

The domains share a hosting element at the observation date. This alone does not establish common ownership.

Check timing, shared infrastructure and other public identifiers; distinguish technical provider from operating organisation.
This exercise illustrates an interpretation error. It describes no real person, organisation or client case.
On the selected provider’s website, in a new tab. IIS does not retrieve, host or display investigation results. Directory filters only filter the editorial catalogue.
The launchpad builds links inside your browser, without sending the query to IIS or storing it in browser storage. Clicking a prepared link sends the query to the named provider, under its own rules.
No. Access may require an account, subscription, software or quota. The catalogue is available in French and English; providers set their interface languages, coverage and conditions.
No. Index coverage, spelling, language, access limits and capture dates can explain a missing result. Record what was searched and what remains unknown.