Tool profile
digga
Check current domain DNS and registration context
Claims and corrections are reviewed before public profile changes.
Editorial proof card
digga
Check current domain DNS and registration context
Best for: Investigators starting from a public domain who need to compare live resolver answers and inspect available registration dates…
Signal summary
Trust / disclosure
How to read this profile
Editorial line
Editorial judgment and commercial context are kept separate on OSINT4ALL.
Review status
This profile has an editorial review date. Source checking does not mean the tool was hands-on tested.
Claims / submissions
Corrections and claim requests are reviewed before any public change is made.
Commercial context
No commercial relationship is disclosed on this profile.
Editorial verdict
Use case and fit
This is editorial guidance, not vendor copy.
Investigators starting from a public domain who need to compare live resolver answers and inspect available registration dates before making an infrastructure pivot.
A useful first lookup for current DNS and registration context. Choose a historical service when the question is how infrastructure changed over time.
Best for checking a public domain's current DNS answers and registration context before following infrastructure leads or comparing historical records.
Operational snapshot
Workflow, access, and coverage
Checking current DNS and domain registration records
Domain
DNS Record, Registration Record
Infrastructure Context
A public-domain test corroborated DNS and RDAP only. Other modules and failure modes were not tested. Record query time and resolver; shared infrastructure or redacted registration data cannot establish common ownership.
Enter the domain, record the time and resolver, inspect DNS and RDAP separately, and corroborate any consequential relationship with the original registry or another relevant source.
The reviewed interface was English. Internationalized-domain handling was not exercised in the public-domain test.
Limits
Strengths, caveats, and risk
The tested DNS and RDAP flow required no account, exposed resolver choices, and returned fields that could be checked against independent DNS and registry responses.
The convenient combined interface does not remove the need to preserve query time, identify the source behind each field, or verify modules separately.
One public-domain test does not establish complete coverage or reliability during outages. WHOIS fallback, TLS, subdomains, email checks and cryptographic DNSSEC validation were not tested.
Domains entered into an online lookup are not private case notes. Shared infrastructure and changing DNS records can produce false ownership links.
Use appropriately scoped public domains and respect service terms. A discovered hostname does not authorize probing or access to the service behind it.
The 3 October 2026 check corroborated DNS and RDAP fields only. A signed-delegation flag is not our independent cryptographic validation of the domain's DNSSEC chain.
Maintenance
Source status & suggest an update
Help keep this profile accurate. Update requests are reviewed and logged before publication.
Source checked: 2026-10-03
If something is outdated, please submit a correction or ownership update request. Claim requests are reviewed and do not grant editorial control.
Commercial or sponsorship requests use the separate partner workflow.