Skip to content

EASM · External attack surface

How exposed is your organisation?

A 23-step review of what anyone on the internet can see about you, using free public tools. Enter your domain and public IPs once and every link below fills in. Mark each check as clean or as a finding, then copy a summary for your team.

Your organisation

Enter the domain you want to review.

Used to search for lookalikes and certificates.

Optional. Without IPs, the per-IP checks stay greyed out.

0 of 23 checks reviewed

Everything stays in your browser: nothing you type here is sent to Citadel, and your progress is saved only on this device. Each link opens the third-party service directly, which then sees the domain or IP in the link. Only check domains and IPs your organisation owns.

1Asset inventory

Build the list of everything that is yours: hostnames, IP ranges and registrations. Every later step works from it.

0/4

Monthly

  • Hostnames in certificate transparency logs

    Every public TLS certificate is logged with the names it covers. Forgotten dev, test, staging and VPN hosts usually show up here first.

    Check with crt.sh
  • DNS records and subdomain map

    Passive DNS services remember hostnames and records seen over the years. Compare them with what you think you run.

  • IP ranges and network owner (ASN)

    Find address blocks registered to your organisation, and confirm who announces each of your public IPs.

  • Domain registration and expiry

    A domain that lapses can be registered by someone else, along with its mail. Check the expiry date, registrar and transfer lock.

2Exposed services

What answers on your public IPs. Remote access, admin panels and databases facing the internet are the usual way in.

0/3

Monthly

  • Open ports and known CVEs per IP

    A quick summary per IP from Shodan's free database, no account needed: open ports, detected products and CVE identifiers.

    Check with
  • Service banners and product versions

    Look for RDP, SSH, VPN portals, firewall and router admin pages, databases, and old firmware versions.

  • Exposed products that attackers exploit right now

    If a product you expose has a CVE on the known-exploited list, attackers are using it now. Patch or remove it first.

3Websites and TLS

Configuration of your public web presence: certificates, protocol versions, security headers and leftovers.

0/5

Quarterly

  • Certificate and TLS configuration

    Expired or mismatched certificates, old protocol versions and weak ciphers. These links hide your results from the public board.

  • Security headers

    HSTS, Content-Security-Policy, X-Frame-Options and X-Content-Type-Options protect visitors against downgrade, clickjacking and injected content.

  • Full site overview

    One page with DNS, redirects, technologies, cookies and security.txt. internet.nl scores the site against current standards.

  • What scanners already recorded about you

    Earlier scans by anyone show pages, scripts and third-party hosts your site loads.

    New scans on urlscan.io are public by default. Set visibility to Unlisted or Private before scanning.

  • Old pages and files in web archives

    Old login pages, documents and scripts that were archived may still be live on your servers.

4Email and DNS

Whether someone can send mail as you, and whether your DNS answers can be trusted.

0/3

Quarterly

  • SPF, DMARC and MX records

    No DMARC, or DMARC with p=none, lets anyone send mail that appears to come from your domain.

  • End-to-end mail security test

    Checks STARTTLS, DANE, SPF, DKIM and DMARC together. Learn DMARC shows how a real message you send is judged.

  • DNSSEC

    Signed DNS stops forged answers for your domain. DNSViz shows whether the chain of trust is complete.

    Check with DNSViz

5Data leaks

Credentials, keys and documents about you that are already public.

0/3

Monthly

  • Company accounts in known breaches

    Lists which company addresses appear in public breach data, so you can force password resets and check MFA.

  • Your domain in public code

    Employees and vendors sometimes publish config files, internal hostnames or API keys in public repositories.

  • Documents indexed by search engines

    Spreadsheets and documents with internal details sometimes get indexed by mistake.

6Brand impersonation

Domains and sites built to look like yours, usually for phishing your customers or staff.

0/2

Monthly

  • Registered lookalike domains

    Typos, swapped letters and other TLDs of your domain that someone has registered, with their mail and web status.

  • Certificates and sites using your brand name

    A new certificate or scanned page with your brand in the name is often the first sign of a phishing site.

7Reputation

Whether your domain or IPs are already flagged, which can mean a compromise and also hurts mail delivery.

0/3

Monthly

  • Spam and abuse blocklists

    A listed mail IP or domain means bounced mail, and sometimes a compromised host sending spam.

  • IP abuse reports

    Reports from other networks about scanning, brute force or spam coming from your addresses.

    Check with Cisco Talos
  • Flagged as malicious or unsafe

    Browsers warn visitors away from sites on Safe Browsing. Antivirus detections on your domain often mean injected content.

8Prioritise and report

After each review

Fix in this order

  1. Exposed products with a CVE on the known-exploited list
  2. Admin panels, remote access and databases open to the internet
  3. Leaked credentials and keys
  4. Expired certificates and lapsing domains
  5. Missing DMARC, or DMARC at p=none
  6. Lookalike domains, headers and other hardening

Your findings

No findings marked yet.

Doing this every month takes hours. Citadel's analysts run these checks continuously for your domains and IPs, watch for new exposure and lookalike domains, and tell you what to fix first. Talk to our CTI team.