Start with what you know.
Bring an authorized domain. Available public sources supply names, addresses and certificate records to investigate.
PUBLIC EVIDENCE. OPEN QUESTIONS.
Follow the connections around a domain. Inspect public DNS, certificate and network evidence, then decide what deserves a closer look.
Private alpha · built by Icarus Online
Two practitioners. One real question each. Honest feedback.
FOLLOW THE EVIDENCE
Two certificates contain the same public key. The second names status.example.net, giving the investigation another domain to examine.
Certificate A → public key → Certificate BSelect a node to inspect its connection. This example queries no target.
DNS & reverse DNS
Certificates & public keys
Network records
A WORKSPACE FOR FOLLOWING A QUESTION
A map is a starting point. What matters is being able to explain the next step.
Bring an authorized domain. Available public sources supply names, addresses and certificate records to investigate.
Inspect the source and collection time. Consider a shared provider or an old record before making an attribution.
Reopen your private investigation, record an assessment and export the evidence. Including your assessment is your choice.
CURIOUS BY DESIGN. CAREFUL WITH CLAIMS.
Shared infrastructure can point to an overlooked service, a provider dependency or an unrelated tenant. Swampcat helps you inspect the observation and keep those alternatives in view.
Why we’re building thisA source record, its collection time and the assets it connects.
An interpretation to check, with alternatives and missing evidence.
Incomplete coverage stays visible. A missing result is not proof of absence.
THE PUBLIC INDEX
Search stored certificate evidence, or open the workspace to start an investigation with the sources available to your account.
HELP SHAPE THE NEXT CHAPTER
We’re inviting two security or OSINT practitioners for a small, supervised alpha. Useful feedback matters more than a polished success story.