Private digital intelligence bureau Lawful OSINT · Cyber monitoring · Due diligence
Specialist reviewing a physical map of public domains and digital services

Infrastructure guide · 14 min

Map public digital infrastructure without mistaking proximity for ownership.

Domains, certificates and network addresses describe dated technical relationships. Linking them can reveal a forgotten asset or an impersonating site, but careless attribution can assign a service to the wrong organisation.

Published Updated Publisher and method: IIS

At a glance

Four rules for a useful review.

  • Start from official brands and domains.
  • Preserve the date and source of each link.
  • Keep observation separate from attribution.
  • Ask the owner to validate uncertain assets.

Step-by-step method

A reproducible path from question to conclusion.

  1. People talking around a table in a cafe — AI-generated photograph
    1

    Set the boundary

    List officially published domains, relevant brands, subsidiaries and countries. Record exclusions and the people authorised to confirm ownership.

  2. A woman adjusts a curtain in her workspace — AI-generated illustration.
    2

    Collect public traces

    Review accessible DNS records, public certificates, web archives and official pages. Record the publisher, observation date and period represented.

  3. Separate workstations in a shared space — AI-generated photograph
    3

    Connect the evidence

    Link each domain, subdomain, certificate, provider and observed page with a precise relationship. Shared hosting or an IP address alone cannot prove common ownership.

  4. A person examining a photograph before describing it — AI-generated photograph
    4

    Grade each asset

    Mark assets confirmed, probable, possible or outside scope. Seek independent confirmation before assigning an asset to the organisation.

  5. 5

    Rank the gaps

    Look for expiring domains, old redirects, forgotten login pages, lookalike names and services without a known owner. Judge actual impact before acting.

  6. A volunteer team planning an activity in a courtyard — AI-generated photograph
    6

    Deliver an actionable inventory

    For each asset, state evidence, date, confidence, owner to confirm and proposed action. Technical corrections belong with the authorised team.

A technical relationship is not proof of ownership

Thousands of sites may share a provider, address or protection service. A certificate may also include an old domain or predate a transfer.

Strong attribution combines an official publication, current configuration, consistent history and, where possible, owner confirmation. Preserve the type and date of every link.

The map needs a timeline

DNS and certificate records change. An archive shows a past state; a current response reflects only the time it was checked. Combining periods without labels creates false relationships.

Record discovery date, last observation and original source. A vanished relationship may still matter to a timeline without being called a current exposure.

Turn the map into defensive decisions

The inventory can find an ownerless asset, clarify an official channel or identify a lookalike domain. It is not permission to probe systems.

Connect each risk to an owner, proportionate action and evidence of correction. An unknown asset first needs internal validation.

Read a DNS alias without attributing content

A CNAME describes a DNS alias, not common ownership. Record queried name, target, answer type, resolver and time. IP prefixes, ASNs and registration organisations describe different layers. Hosting providers may serve many customers without controlling their content.

Document the map’s period of applicability

Retain available first and last observations, source and coverage. Recent consultation does not refresh historical evidence. Have authorised owners confirm important assets. After migration, distinguish control of the domain, service and recovery channels.

Reading technical evidence

Date an RDAP event rather than a website’s activity

An RDAP response pairs an event type with a date. Retain both fields together.

Field or situation and its interpretation
Observed itemWhat it means
eventAction: registrationRegistration event for the object; it does not date the website’s first publication.
eventAction: last changedA change to the registered object; it does not prove a change of owner.
eventDateRead 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.

RFC 9083, § 4.5

Read the original record

Identify the object described by an RDAP response

An RDAP response describes a registered object. Retain its type and the queried authority rather than labelling every field owner.

Fields to retain and interpretation limits
ItemRecord to retainLimit
ObjectobjectClassName, handle and ldhName where present.A domain object is not an IP-network object.
EntitiesDeclared roles and available identifiers.Registrar, technical contact and registrant have different roles.
EventseventAction with eventDate, plus consultation time.An update does not prove that the website was sold.

RFC 9083 — JSON Responses for RDAP

Worked example

Two domains use the same hosting IP

Fictional teaching case, not a client investigation.

Does this technical relationship establish a shared operator?

Observation, interpretation and limit
ObservationWhat it establishesWhat remains unproven
A DNS observation associates two domains with one IP.A technical relationship is observed at the check time.Shared hosting can explain it without common control.
A historical certificate mentions one domain.A certificate trace exists for that name and period.It does not automatically confirm current configuration or the other domain.
An official organisation document confirms only one domain.That domain has documentary attribution in the consulted source.The other remains insufficiently attributed.

Conclusion to record

Represent a dated hosting relationship, not ownership. Mark the confirmed and unattributed domains separately.

What would change the conclusion?

Seek explicit attribution or an authorised owner’s confirmation; refresh relevant technical observations.

Check your reasoning

Can a “same IP” edge become “same company” without a new source?

· Open the verification log

Your working sheet

Turn the method into a documented review.

For each point, record what the material actually supports. “Supported” applies to the specific observation, not to the entire case. A contradiction needs explanation; missing material remains an open question.

  1. Define the question
  2. Record the source
  3. Test the observation
  4. State the limits

Entries stay in this page until you leave or reload it. Nothing is saved or submitted by this tool. Use neutral references instead of personal data or credentials.

1. DNS

Record type, resolver, value and observation time.

Limit: A current answer does not describe the full domain history.

2. Hosting

Observed address, ASN and association source.

Limit: CDNs, cloud and shared hosting limit attribution.

3. Certificates

Covered names and logging or validity dates.

Limit: A logged certificate does not prove a currently active service.

How to write a useful conclusion
Editorial examples, not findings about your case
MaterialUseful wordingNext check
One dated sourceThe consulted source stated X on the recorded date.Check its origin and whether it still applies.
Multiple copies of one claimSeveral pages repeat X; independent corroboration is missing.Find the original and a source with independent evidence.
Conflicting sourcesA states X while B states Y; the difference is unresolved.Compare dates, scope, identifiers and definitions.
No matching resultNo result was found in the recorded scope.Describe queries, coverage and access limitations.

What to check and what to record

Use this grid to turn the method into a reviewable case file. A missing item remains an open question. The interpretation limit prevents a finding from becoming an unsupported conclusion.

Topic-specific checks
CheckUseful recordInterpretation limit
DNSRecord type, resolver, value and observation time.A current answer does not describe the full domain history.
HostingObserved address, ASN and association source.CDNs, cloud and shared hosting limit attribution.
CertificatesCovered names and logging or validity dates.A logged certificate does not prove a currently active service.

Common pitfalls

Four shortcuts that weaken the result.

Attributing by IP

A shared address may connect unrelated organisations.

Treating archives as current

An old capture does not establish an active service.

Scanning without permission

Open-source mapping does not authorise testing systems.

A chart being explained with its context document — AI-generated photograph

Publishing a sensitive inventory

The list could aid impersonation; limit its circulation.

Practical questions

Frequently asked questions.

Can a certificate identify a domain owner?

It can provide a clue, but its names and date alone do not establish current ownership.

Does a shared IP mean a shared organisation?

No. Shared hosting, content delivery and protection services make this inference unreliable.

Should a scan be used to complete the map?

Only under a separately authorised technical scope. This guide uses public traces and owner validation.

Public references

These primary references support the checks described here. The sequence and working sheet are an IIS editorial method; a cited organisation does not endorse this guide. Read each reference within its stated date, jurisdiction and scope.

ICANN — RDAP. Official context for domain registration lookup and its limits.

RFC 1034. Reference for the technical fields and interpretation boundaries described in this guide.

Editorial scope

Published by Internet Intelligence Service on 23 September 2026. Last content update: 29 October 2026. This educational guide describes a lawful, defensive method. It is not legal advice, an emergency service or authority instruction.

Find primary portals and their limitations

Editorial responsibility, examples and corrections