You don’t need a security team to get a first picture of what your business exposes to the internet. This checklist takes about half an hour, needs no special software, and tells you where the surprises are. Run the checks only against domains and addresses that belong to your business.

The checklist

1. List your domains

Check the domain registrar account, the invoices and the email system. Write down every domain, including old campaign domains and ones that only exist for email. Note who owns each registrar account and whether it has multi-factor authentication.

2. Check that domains will renew

An expired domain can be registered by someone else, who then receives your mail and impersonates you. Confirm the expiry date and turn on auto-renew for domains you still need.

3. List subdomains

Open your DNS provider’s control panel and list the records. Then search a certificate transparency log such as crt.sh for your domain, to see subdomains that have had a certificate issued. Mark every name nobody can explain.

4. Open each subdomain in a browser

What does it show? Flag login pages, default server pages, test or staging sites, and anything that looks abandoned.

5. Check certificates

Look for certificates that have expired or will expire within 30 days. Browsers show a warning to visitors, and some systems simply stop working.

6. Check email authentication records

Look up your domain’s SPF, DKIM and DMARC records (free web checkers exist). Without them, anyone can send mail that appears to come from your domain.

7. Review the router or firewall rules

Look for port forwards and rules that allow any source address. Each one should have a named owner and a reason. See our guide on exposed remote access.

8. Check your public IP addresses from outside

From a network outside your office, check which ports answer on the addresses you own. Anything you can’t explain, such as remote desktop, a database or an admin panel, needs an answer.

9. Update the software that faces the internet

Website platform and plugins, VPN, firewall firmware, the router. Outdated, internet-facing software is a favourite target.

10. Write it all down

A simple table is enough: asset, what it is for, who is responsible, last checked. This list is the beginning of the system map that data security regulations expect you to keep.

What to do with the results

Sort the findings in three groups:

  • Close now: anything nobody uses, especially open remote access and abandoned test sites.
  • Fix this month: expired or expiring certificates, missing email records, outdated software.
  • Assign an owner: everything left, so every asset has a person responsible.

The limits of a manual check

A manual pass is a snapshot. It misses subdomains that no public source lists, it can’t scan ports at scale, and it is out of date the next time someone opens a port or launches a site. Teams that repeat it find that the hard part isn’t doing it once, it’s remembering to do it again. That is the gap continuous monitoring is built for: the same checks, on a schedule, with an alert when something changes.

A clean checklist today is a good start. What matters is whether it is still clean next month.