Attack Surface Management Included in Free

Find forgotten subdomains before attackers do.

Every public certificate is logged in Certificate Transparency logs. Cysoro uses those logs to list the hostnames your organization has exposed, checks which are live, finds broken HTTPS, and flags subdomains that point to services you no longer control.

The problem

  • Old staging sites, marketing microsites and test hosts are easy to forget — and easy to attack.
  • A DNS record that still points to a deleted cloud resource (S3, Azure, Heroku, GitHub Pages…) can be claimed by someone else: subdomain takeover.
  • Attackers enumerate these logs too; you should see what they see.

How it works

  1. Open a domain and choose Attack surface.
  2. Cysoro pulls hostnames from CT logs; DNS and HTTPS checks run from your browser.
  3. Remove stale records, re-claim or delete dangling ones, and fix broken HTTPS.

What you get

Subdomain discovery

Hostnames from public Certificate Transparency logs, including wildcard certificates.

Live host check

A, AAAA and CNAME resolution for every hostname.

Takeover-risk detection

Dangling CNAMEs to 30+ cloud and SaaS services whose target no longer exists.

HTTPS health per host

Which live hosts fail HTTPS.

Saved history

Each run is saved so you can compare over time.

Try it free, no account

Single-check versions of this module.

What Cysoro checks

Every check, what we look for, and why it matters.

CheckWhat we look forWhy it matters
Subdomain discoveryEvery hostname in public Certificate Transparency logs for your domainShows assets your team may have forgotten
Wildcard certificatesWildcard names such as *.dev.acme-example.comWildcards hide how many hosts exist behind them
DNS resolutionA, AAAA and CNAME for each hostnameSeparates live hosts from stale log entries
Subdomain takeoverCNAMEs to 30+ services (S3, Azure, Heroku, GitHub Pages, Netlify, Shopify…) whose target no longer resolvesAn attacker can claim the target and serve content on your subdomain
HTTPS per hostWhether each live host completes an HTTPS requestBroken HTTPS on a forgotten host is a sign it is unmaintained

Example result

Illustrative output for a fictional domain.

At risk
Takeover risk: promo.acme-example.comCNAME → acme-promo.herokuapp.com, which no longer exists.
Review
Live but HTTPS fails: old-staging.acme-example.comResolves to 203.0.113.20; HTTPS did not complete.
Info
Stale in logs: beta.acme-example.comCertificate issued in the past; no DNS record now.
Passed
38 hosts resolve and serve HTTPSLast run today.

When teams use it

Cleaning up after a migration

Find DNS records still pointing to old hosting or cloud resources.

M&A and new clients

Get a quick view of a domain's internet-facing footprint.

Quarterly hygiene

Re-run every quarter and remove what nobody owns.

Data sources & how it runs

  • Certificate Transparency logs via Cert Spotter (crt.sh fallback)
  • DNS over HTTPS from your browser
  • One no-cors HTTPS request per live host from your browser

Limits, honestly

Hosts that never had a public certificate do not appear in CT logs. Cysoro does not scan ports or brute-force subdomain names.

Questions

Does this scan ports or probe my servers?

No. It reads public logs and DNS and makes one normal HTTPS request to live hosts. No port scanning.

Will it find every subdomain?

It finds every hostname that appears in public certificates, which covers most internet-facing sites. Hosts with no certificate do not appear.

How many hosts are checked?

Up to 100 hostnames per run are resolved, and up to 40 live hosts are tested for HTTPS.

What should I do with a takeover risk?

Delete the DNS record if you no longer use the service, or re-create the resource on the service so you own it again.

See where your domain stands

Free for up to 3 domains. No card, no installs.

Start free