invite-only · defensive use

See what is exposed on the servers you own.

Vigil verifies you control a domain, scans only the servers under it in isolated containers, matches the services it finds against CVE data, and hands you the exact patch steps for your OS. For systems you own - no third parties, no active scans.

Access is by invite. Vigil is for patching servers you own and have verified.

01 // ownership verification

Prove you own it before we scan it.

Every domain starts locked. You publish a DNS TXT record, we confirm it, and only then does scanning unlock. This is the gate that keeps any scan from ever running before you have shown control of the target.

scanning only on verified assets

  1. 01

    Add the TXT record

    Vigil hands you a DNS TXT record for your domain, for example _vigil.api.example.com.

  2. 02

    We verify ownership

    We resolve the record and confirm you control the domain. We will not touch a domain without this proof.

  3. 03

    Unlock scanning

    Scanning enables for the verified domain and the servers under it. Everything after this runs on assets you own.

02 // features

What Vigil does with a verified server.

Domain ownership verification

You prove control of a domain with a DNS TXT record before any scan runs. No asset is touched until ownership is confirmed, and never a third party you do not own.

dns txt · proof

Isolated worker containers

Every scan runs in a sandboxed worker container. Port discovery via naabu, service and version detection via nmap -sV, run only against your verified assets.

naabu · nmap -sV

Passive intelligence

Enrichment pulls from Shodan and Censys lookups. Passive by design - you gain context on your own ports and services without actively scanning anyone else.

shodan · censys

CVE matching

Detected service banners are matched against NIST NVD and OSV data. Findings come back with a CVE reference and a severity rating you can act on.

nist nvd · osv

OS-specific remediation playbooks

Each finding carries exact patch and hardening steps written for the target OS - apt for Debian and Ubuntu, dnf for RHEL and Rocky, plus Windows Server guidance.

apt · dnf · windows

Alerting

Findings push where you already work. Send alert payloads to a webhook or straight to Telegram so a serious CVE lands in front of you, not in a log you never open.

webhook · telegram

03 // sample finding

A finding, and the exact fix for your OS.

illustrative sample data
findingseverity high

CVE-2024-7347

nginx nginx 1.24.0

asset
api.example.com
service
nginx · :443
os
ubuntu 22.04 lts
source
nist nvd · osv
detected
2026-11-18 04:12 UTC
networkdenial of servicepatch available
remediation playbook · ubuntugenerated for this host
sudo apt update && sudo apt list --upgradable
sudo apt install --only-upgrade nginx
sudo apt install --only-upgrade openssh-server
sudo systemctl restart nginx ssh
vigil verify --asset api.example.com

run to patch: sudo apt update && sudo apt upgrade. verify with vigil scan after.

This finding is sample data shown for illustration. Real findings are generated from live scans of servers you own and verified.

04 // alerting

A high-severity CVE should reach you, not a log.

Vigil pushes findings to the places you actually check. Set one destination per account or per server, and get the context you need in the alert - not just a trigger.

Webhookhttp/json

Post a JSON payload to any HTTP endpoint when a finding lands. Point it at your ticketing, chat, or automation.

Telegrambot → chat

Push a message to a Telegram chat or group. Payload carries the service, the CVE, severity, and the asset it affects.

05 // faq

Questions, answered plainly.

Is Vigil invite-only, and how do I get access?

Yes. Access is by invite so every account maps to a real operator and every scanned asset is owned and verified by that account. Request an invite through the form below and we review requests in order.

How does domain verification work?

After you add a server, Vigil gives you a DNS TXT record to publish on the domain. We check the record, and only when it resolves do we unlock scanning for that domain and the servers under it.

What does Vigil scan, and how is that safe?

Vigil only runs scans against assets you have added and verified. Each scan executes in an isolated worker container using naabu for port discovery and nmap -sV for service detection. Nothing is scanned until ownership is confirmed.

Are scans active against anyone else?

No. Service and version detection run only against your verified servers. Enrichment from Shodan and Censys is passive lookups against your own ports and services. We never actively scan third parties.

How are CVE findings generated?

The service banners we detect are matched against NIST NVD and OSV vulnerability feeds. A match returns a CVE reference, a severity rating, and links back to the source data so you can review the reasoning yourself.

What does a remediation playbook contain?

Patch commands written for the target OS, exact package names, and hardening steps - for example apt get for Debian and Ubuntu, dnf for RHEL and Rocky, or a step list for Windows Server. It reads like a checklist, not a paragraph.

How do I get alerted on new findings?

Point an alert destination at a webhook URL or a Telegram chat for either your whole account or a specific server. New findings push to that destination as they are detected.

Is Vigil only for defensive use?

Yes. Vigil is a defensive security tool for inspecting and patching servers you own and have verified. It is not built for attacking or scanning systems without authorization.

request an invite

Get on the list.

Vigil is invitation-only. Leave your work email and your team, and we review requests before issuing access. By requesting, you confirm the systems you want to monitor are yours.

No spam. We only email you about your invitation.