PylonMon
Attack surface monitoring

See what’s exposed before
attackers do.

Discover and monitor your external attack surface so you can find risks early, fix misconfigurations, and keep your business secure.

No credit card required.

Your attack surfaceexample.com · scanned 3 times a day
✓Certificate valid · chain unchanged
✓Nameservers and mail records unchanged
!SPF is not enforcing
✓Not on any blocklist
!tcp/3389 newly open
Scanning…
Find Risks
Fix Issues
Stay Ahead!
Buddy, the PylonMon mascot
Discover what showsCertificates, DNS, mail authentication, reputation, open ports.
Detect risksBroken chains, records that moved, ports that opened, blocklists.
Get alerted on changeBe the first to know when the surface changes, not on every scan.
Built for teamsShare visibility, manage access, and keep your organization secure.
Example findings
AssetsOpen portsRisksCertificates
app.example.com3.12.45.67
api.example.com3.12.45.68
dev.example.com18.23.11.45
blog.example.com54.23.12.11
mail.example.com35.12.98.76
Global visibility

See your surface the way
an attacker sees it.

Certificates, DNS, mail authentication, reputation and open ports, scanned from outside your network three times a day. You are told when something changes, not on every scan.

Learn more about attack surface monitoring →
Works well with
CloudflareAWSGoogle CloudDigitalOceanGitHub Pagesany DNS host
A smaller attack surface is a safer business.

Continuous attack surface monitoring helps you reduce risk, prevent incidents, and stay compliant.

Get Started Free →
No credit card required.
More about attack surface monitoring

How exposure monitoring works

1 · WATCH

Public surface, from outside

Every asset gets the same checks three times a day: TLS certificate and chain, DNS and mail records, SPF/DMARC enforcement, and Spamhaus blocklist reputation. Public data only — nothing touches your servers.

2 · VERIFY

Prove it, unlock ports

Prove you control a host — a DNS TXT record, a well-known file, or one curl from the box — and open-port monitoring turns on: ~35 common ports, and a hard flag on anything that should never face the internet (RDP, SMB, bare databases).

3 · PAGE

Change-based alerts

The first scan is the baseline; after that you hear when something appears or clears — a port opening, a chain breaking, an IP landing on a blocklist. One open port never becomes three pages a day.

The signals, spelled out

  • TLS certificates — expiry countdown plus real chain validation: self-signed, private CA, a missing intermediate, or a hostname the certificate doesn't cover.
  • DNS records — nameservers and mail routing, diffed against baseline. A domain quietly moved to registrar parking is exactly this signal.
  • Email authentication — SPF and DMARC present, and SPF actually enforcing (-all) rather than soft-failing.
  • Reputation — your addresses checked against the Spamhaus ZEN blocklist, before your customers' mail servers tell you the hard way.
  • Open ports — reported as opened/closed changes against an expected list you control. Deliberate ports are marked expected once and never alert again.

From your first domain to the whole fleet

These are the same signals the big attack-surface platforms sell — the difference is you can be watching your first domains five minutes from now, free, and the same system carries all the way up: escalation ladders on every plan, on-call rotations on Team, and on Enterprise your BYO-AI agent receives every exposure alert as a structured envelope and investigates before you're awake. MSPs and platform teams run every client domain in one workspace with per-asset alert routing.

Why change-based beats scanning reports: a monthly PDF of everything that's open tells you what you already meant to expose. The finding that matters is the delta — the port that opened last night, the cert that stopped validating today, the SPF record someone "simplified." That's what pages you here.

Common questions

Do you scan my servers?

Not without proof. Certificates, DNS, mail auth and reputation are public records — those run on any domain you add. Port scanning sends traffic to the host, so it only runs on assets whose ownership you've verified, and it probes a fixed, bounded list — not an exhaustive sweep.

What can I watch?

Public domains, hostnames, and public IP addresses. Private ranges and internal-only names can't be seen from the internet — cover those with the agent and normal uptime monitors in the same account.

What does it cost?

The free plan includes 3 exposure assets with full alerting, alongside your uptime monitors. Paid plans raise the asset count and start at $9/mo. See pricing →

How is this different from my uptime monitor?

It's the other half. Uptime tells you when the site stops answering; Exposure tells you when what it's showing the world changes — an expiring chain, a hijacked record, a port that shouldn't exist. One account, one place that pages you, for both.

Watch your first 3 domains free →

Nothing to install. No credit card.