Exposures worth a look
Admin panels, dev and git hosts, open remote access and file transfer services, verbose error pages.
Potential CVEs
Recent vulnerabilities from the Ethiack Zero feed, matched to detected versions. Marked likely or possible. Never claimed as proven.
Technologies and third parties
Web servers, frameworks, CDNs and hosting providers behind each subdomain.
Subdomains, grouped
Every subdomain we can see, grouped by fingerprint. A hundred identical redirects read as one line.
Questions
How do I check my domain’s exposure to vulnerabilities?
Enter your domain. The check maps your public subdomains, services and technologies, then matches them against recent CVEs. It takes 1 to 5 minutes.
What is the difference between vulnerable and exploitable?
Vulnerable means a detected version matches a known CVE. Exploitable means an attacker can actually use it in your environment. Only testing proves the second.
Is every vulnerability a risk?
No. A vulnerability becomes a risk when an attacker can exploit it in your environment. Ethiack tests each one to prove which are real.
Is a non-intrusive exposure check safe?
Yes. It uses public sources and one standard HTTP/HTTPS request per subdomain. No active testing, no exploitation, no load on your systems.
What does it not cover?
Mobile apps, internal networks and assets outside the domains you enter.
What you expose.
This check, a first look
Matched against recent CVEs from the Ethiack Zero feed; older vulnerabilities aren't checked. Likely: the detected version is in an affected range. Possible: it can't be confirmed or ruled out.
Technologies
| Subdomain | Status | Title | Server | Technologies | Risk | TLS |
|---|
No subdomains match the current filter.