Organizational Breach & Exposure History – The Public Record on Another Company, Before You Sign
By purchasing you agree to our Terms of Service, including your responsibility to run scans only against systems you own or are authorised in writing to test.
Before you give a supplier access, buy a company or sign a contract: what does the public record already say about them?
The Organizational Breach & Exposure History assembles what the public record shows about one organisation you name — the data breaches it has been named in, what its published email and DNS settings say about how it is run, its certificate history and the suppliers behind its names, lookalike domains registered against it, public code repositories under its name, whether it publishes a security contact, and whether it appears in public criminal leak listings. It does not scan them. It visits their website at most three times, as an ordinary browser would, and everything it reports carries its source and the date it was retrieved.
What it checks
- Public breaches naming this organisation, corroborated across more than one index before they are reported
- What their published email and DNS settings say about how the organisation is run
- Their certificate history and the suppliers behind their names
- Lookalike domains registered against them, and which of those can send email
- Whether they publish a security contact, and public leak listings that name them
- Public code repositories under their name, and the history of their web presence
What you get
- A written PDF report emailed back to you, typically within one business day.
- Every finding rated Critical / High / Medium / Low, each with its source and retrieval date, and any Critical finding held for human review before it is sent.
- A red-flag summary ordered by what would change a price, a warranty or a decision.
- The question each red flag should make you ask them, which is what a screen like this is actually for.
- A "what was checked" appendix that states the limits of the scan honestly.
- Reporting built to CompTIA Security+ and PenTest+ practice standards.
Who it's for
Buyers, brokers, advisors and anyone onboarding a supplier who wants access to their systems. It is a screening tool: it tells you whether to commission a full engagement and what to ask in it.
Requirements
- Windows 10 or Windows 11
- No administrator rights needed
- An internet connection
- The organisation's legal name and its main domain, typed twice
- About 5 minutes
- You must own or control the organisation, or hold written authorisation or a signed engagement covering it — you state which, it is recorded on the report, and there is no third option
What this is not
QuickScan is detection and advisory only. This product never scans, probes, tests or logs in to the organisation you name; it reads public records and makes at most three ordinary page requests to their website. It does not assess that organisation's security and cannot tell you whether their internal controls are sound. It is not cyber due diligence and is not a substitute for it. It is not a certification, an audit or an attestation. The report describes what the public record shows, as at the date it was retrieved, from the sources it names — nothing more.
One-time purchase. No subscription, no auto-renewal. Your report is prepared with AI-assisted analysis under ThreatVector's security review protocols and checked against our false-positive triage rules before it is sent. Reports are produced by ThreatVector LLC. ThreatVector and its scan library are developed, sold and distributed by ThreatVector LLC.
TommyGun is developed by ThreatVector LLC. Reporting mechanisms and cybersecurity customer service are powered by ThreatVector LLC. ThreatVector and its scan library are developed, sold and distributed by ThreatVector LLC.