Drill through any domain.
Strata reads one domain through six layers of public record, then counts what else stands on the same infrastructure.
Sample run: drilling johndoe.example
johndoe.example sample Bedrock reached Reached
Registrationsample
- Registrar
- Example Registrar, Inc.
- Created
- 2014-03-09
- Expires
- 2027-03-09
- Registrant
- redacted for privacy
DNSsample
- A
- 203.0.113.24
- MX
- 10 mail.johndoe.example
- NS
- ns1.example.net · ns2.example.net
- TXT
- v=spf1 include:_spf.example.net ~all
Certificatessample
- Subject
- johndoe.example
- Names
- www · shop · pay · +9 more
- Issuer
- Example Trust CA 2
- Valid
- 2026-09-14 to 2026-12-13
Hostingsample
- Address
- 203.0.113.24
- Network
- 203.0.113.0/24
- ASN
- AS64500 · EXAMPLE-HOSTING
- Reverse
- web-24.example.net
Mailsample
- MX
- mail.johndoe.example
- Mail host
- mx.example.org
- Address
- 198.51.100.7
- Policy
- SPF ~all · DMARC p=none
Historysample
- 2014-03
- registered, Example Registrar
- 2019-06
- nameservers moved to example.net
- 2023-11
- 192.0.2.80 → 203.0.113.24
47other domains stand on
the same bedrock
samplenot reached yet
- 31same server
203.0.113.24 - 9same certificate
1 certificate - 7same mail host
mx.example.org
The 47 names are in the app.
Six layers. Six answers.
Each layer is one kind of public record. Strata reads them top to bottom and keeps the source and the date next to every row.
01Registration
Who registered it, and when?
Registrar, creation and expiry dates, status codes, and the registrant where the registry publishes one.
RDAPWHOIS02DNS
Where does the name point?
Addresses, mail exchangers, nameservers and text records, read from public resolvers.
AAAAAMXNSTXTCNAME03Certificates
Which names share its certificates?
Every certificate issued for the domain in public transparency logs: names, issuer, validity dates.
CT logsSANissuer04Hosting
Whose network is it on?
The address, its network block, the autonomous system that announces it, and reverse DNS.
IPCIDRASNPTR05Mail
Who carries its mail?
Mail hosts and where they resolve, plus the SPF and DMARC policy the domain publishes.
MXSPFDMARC06History
What changed, and when?
Earlier registrars, nameservers, addresses and certificates, in date order.
first seenlast changed
What Strata never does.
Public data only. These are promises about the product, not switches in a settings page.
-
Never:
scan portsNo scanning.
No port sweeps, no service fingerprinting, no probing for weak spots. Strata is a reader, not a scanner.
-
Never:
log inNothing behind a login.
No accounts, no private panels, no leaked databases. If a record is not public, it is not in the core.
-
Never:
knock on the serverNo noise on the target.
Answers come from registries, resolvers and certificate logs. Beyond ordinary public lookups, nothing is sent to the target’s servers.
-
Never:
guessNo guesses.
Every row shows its source and the date it was read. When a record is missing or redacted, the layer says so.
Before you drill
01What does Strata read?
Public records about a domain: registration data, DNS, certificate transparency logs, network and routing registries, and published mail policy. They are the same sources anyone can query by hand, one at a time.
02Can it see private things?
No. It has no way into accounts, internal networks, private panels or redacted registrant details. When a registry hides a name, Strata shows it as hidden.
03Where do the results go?
They stay on your PC. There is no account and no cloud copy. Export a core as a file when you need to hand it to someone.
04Is this allowed?
Reading public records is something anyone can do by hand, and it is routine work for security teams, journalists and due-diligence checks. Follow each source’s terms of use and your local law. Do not use Strata to harass anyone.