Most organisations cannot say how many domains they own, who controls them or when they expire, yet every one of those domains, and every lookalike an attacker registers, is a route to fraud against their staff, customers and suppliers. Business email compromise, invoice redirection, credential phishing and brand impersonation all depend on a domain that looks like yours or used to be yours. This guide treats the problem as a portfolio discipline: inventory and ownership, registrar and registry protection, defensive registration choices, locking down domains that do not send email, monitoring for lookalikes, takedown routes, and the controlled use of lookalike domains for your own security testing under the M3AAWG September 2025 best practices. It is written for security, IT and brand protection teams and for whoever runs the registrar accounts. Lookalike techniques themselves are explained in the Typosquatting and Lookalike Domains Guide, and the step-by-step takedown process in the Brand Impersonation and Lookalike Domain Takedown Playbook; this page is about running the portfolio.
Key takeaways
- Centralise ownership first. The UK NCSC recommends a single internal group acting as the registrar, more than one trusted person with access, domains managed by your organisation rather than a web host, and kept proof of ownership.
- Expired domains are inherited trust. A domain you let lapse can be bought by anyone, along with the allowlists, links and email that still point at it; set auto-renew on an organisational payment method.
- Every domain that does not send email should say so. Publish
v=spf1 -all, a DMARCp=rejectrecord, a null DKIM key and a null MX (RFC 7505) so the domain cannot easily be used to spoof your mail. - You cannot register every lookalike, so monitor. Combine permutation scanning, certificate transparency monitoring and newly registered domain feeds, and triage by whether a domain has MX records, certificates or live content.
- Takedown routes differ in speed and remedy. Registrar and host abuse reports are fastest for active phishing; the UDRP can only cancel or transfer a domain and requires proof of all three of its paragraph 4(a) elements.
Why the portfolio is a security asset
| Exposure | How it is abused | MITRE ATT&CK v20 | Portfolio control |
|---|---|---|---|
| Lookalike of your domain | Phishing links, fake invoices and supplier impersonation from a domain one character away | T1583.001 Acquire Infrastructure: Domains; T1566.002 Spearphishing Link | Defensive registration of the highest-risk variants, monitoring, takedown |
| Expired or abandoned domain | Re-registered and used to receive misaddressed email, serve content from trusted links or satisfy allowlists | T1583.001 | Auto-renew, retirement process with a holding period |
| Hijacked registrar account | Nameservers changed, traffic and email redirected, certificates issued | T1584.001 Compromise Infrastructure: Domains | MFA on registrar accounts, registrar and registry lock, change monitoring |
| Non-sending domain without email policy | Spoofed mail using your real but unused domain | T1566 family | Null SPF, DMARC reject, null DKIM, null MX |
| Dangling DNS records | Subdomain takeover when a referenced service or domain expires | T1584.001 | Remove unused delegations and CNAMEs (NCSC) |
The lifecycle risk is not hypothetical. In the ForcedLeak research, an expired domain still listed in Salesforce's content security policy as trusted was bought for about five dollars and became an exfiltration channel. Any domain that appears in allowlists, OAuth redirect URIs, webhooks or email routing is part of your trust boundary for as long as those references exist.
Inventory and ownership
- Find every domain: registrar account exports, finance records of domain payments, DNS zones you host, certificates issued for your names (certificate transparency search), marketing and regional teams, and acquisitions. Shadow domains registered on personal cards by agencies or product teams are the usual gap.
- Record the facts per domain: registrar, registrant organisation, account owner and backup owner, expiry date, auto-renew status, payment method, DNS host, whether it sends email, what services use it, and its risk tier.
- Consolidate: move domains into organisational registrar accounts, ideally with one or two registrars that support MFA, role-based access and locks. The NCSC notes that the domain should be managed by your organisation and not the hosting company.
- Tier the portfolio: Tier 1 domains carry email, sign-in, payments or customer traffic; Tier 2 carry active but lower-impact sites; Tier 3 are defensive or parked registrations.
- Keep proof of ownership: registration documents and trademark records, which you will need for a recovery or a dispute.
Protecting the domains you own
| Control | Tier 1 | Tier 2 | Tier 3 (defensive, parked) |
|---|---|---|---|
| Registrar account MFA for all administrators (NCSC) | Required, phishing-resistant where offered | Required | Required |
| Registrar lock (transfer and update protection) | Required | Required | Required |
| Registry lock (changes need out-of-band verification with the registry, may cost extra) | Strongly recommended | Consider | Not usually needed |
| Auto-renew on an organisational payment method | Required, multi-year term | Required | Required, or explicit retirement decision |
| DNS record change monitoring (NS, A, MX, service records) | Required, into the SIEM | Required | NS changes only |
| Certificate transparency monitoring | Required | Required | Recommended |
| Email authentication | SPF, DKIM, DMARC at enforcement | SPF, DKIM, DMARC at enforcement | Non-sending records below |
The NCSC also advises knowing your registrar's procedure for reclaiming a hijacked domain before you need it, and monitoring for listing on DNS blocklists. For registrar hardening in depth see the Authoritative DNS and Registrar Account Security Guide, and for an active hijack the Domain Registrar Compromise Playbook.
Locking down domains that do not send email
GOV.UK guidance for domains that do not send email gives a complete set of records. Adapt the DMARC reporting address to your own:
| Record | Host | Value |
|---|---|---|
| SPF (TXT) | @ | v=spf1 -all |
| DMARC (TXT) | _dmarc | v=DMARC1;p=reject;sp=reject;adkim=s;aspf=s;fo=1;rua=mailto:<your reporting address> |
| DKIM null key (TXT) | *._domainkey | v=DKIM1; p= (and revoke existing selectors) |
| Null MX | @ | Priority 0, value . |
RFC 7505 (Standards Track) defines the null MX: a single MX record with preference 0 and a zero-length label, with no other MX records. It tells senders on the first attempt that the domain accepts no mail. RFC 7505 also notes that a null MX should not be published for domains used in MailFrom or From addresses. If a subdomain of a non-sending domain does send mail, GOV.UK advises sp=none at the parent and full anti-spoofing controls on that subdomain.
Defensive registration: what to buy and what to skip
Registering every variant is impossible: permutation tools routinely generate thousands of candidates for one name. Defensive registration should be targeted at variants that would be most convincing in an attack on your own staff and customers.
- Buy: your core brand in the main country-code TLDs where you trade, the most common typing errors of your primary email domain (character omission, transposition, adjacent keys), obvious hyphenation and "secure", "login" or "pay" combinations if you run customer sign-in or payments, and homoglyph variants of short brand names in the scripts your customers use.
- Skip or monitor instead: long-tail TLDs where you have no customers, combinations with generic words, and internationalised variants your users are unlikely to see.
- Configure what you buy: park defensive registrations with the non-sending email records above and no content, or redirect to your main site over HTTPS; never leave them pointing at a registrar parking page full of advertising.
- Budget by tier: a small business may register only its own name in two or three TLDs plus a handful of typos of its email domain; a large brand owner will run a managed defensive portfolio with an annual review that drops registrations that no longer earn their cost.
Unicode Technical Standard #39 (Unicode Security Mechanisms, version 18.0.0 dated 27 August 2026) defines the confusable "skeleton" comparison and mixed-script detection that browsers and registries use to flag homoglyph domains; its skeleton test is also a good way to rank which internationalised variants of your name are genuinely confusable.
Monitoring for lookalikes
| Method | What it finds | Limits |
|---|---|---|
| Permutation scanning (for example dnstwist) | Registered permutations of your domains: typos, homoglyphs, bitsquats, added words, alternative TLDs; can flag MX hosts and compare page similarity with fuzzy and perceptual hashes | Only finds variants its algorithms generate; heavy DNS query load |
| Certificate transparency monitoring | Certificates issued for names containing your brand, often before a phishing site goes live; NCSC also recommends it for spotting unexpected certificates on your own domains | Misses sites without TLS or using wildcard certificates on unrelated names |
| Newly registered domain feeds | Fresh registrations matching brand keywords | Coverage varies by TLD and data provider |
| Email and DMARC telemetry | Lookalike sender domains in inbound mail, spoofing attempts against your own domains in DMARC aggregate reports | Sees only mail that reached you |
| User and supplier reports | Domains used in live campaigns | Reactive |
Triage signals: a lookalike with an MX record can receive replies and misdirected mail, which the dnstwist documentation calls rogue MX detection; a lookalike with a fresh certificate and a login page is an imminent phishing risk; a parked lookalike with no records is a watch item. Feed confirmed malicious domains into email gateway and protective DNS blocklists the same day. See the Protective DNS Guide.
Takedown and dispute routes
| Route | Best for | Outcome |
|---|---|---|
| Hosting provider abuse report | Live phishing content | Content removed; domain remains |
| Registrar abuse report | Domains used for phishing or malware | Suspension at the registrar's discretion under its abuse policy |
| Blocklist and browser protection reports | Reducing exposure while takedown proceeds | Warnings and blocks for users of participating services |
| UDRP complaint to an ICANN-approved provider | Clear cybersquatting where you want the domain | Cancellation or transfer only (paragraph 4(i)) |
| Uniform Rapid Suspension (URS) | Clear-cut infringement where suspension is enough | Lower-cost, faster suspension; ICANN lists ADNDRC, MFSD and NAF as providers |
| Court action | Complex or high-value disputes | As ordered |
Under UDRP paragraph 4(a) the complainant must show that the domain is identical or confusingly similar to its mark, that the registrant has no rights or legitimate interests in it, and that it was registered and is being used in bad faith. Paragraph 4(b) lists bad faith examples, including registering to sell to the mark owner and using the domain to attract users for commercial gain by creating confusion. ICANN's UDRP page records an updated policy version dated 21 February 2024 with implementation by 21 August 2025. This guide summarises dispute routes and is not legal advice; involve counsel before filing.
Using lookalike domains for your own security work
Security teams register lookalikes too: for phishing simulations, spam traps and sinkholes. The M3AAWG Best Practices for Use of Look-Alike Domains for Security Purposes (22 September 2025) covers this case specifically and excludes pure brand-protection registrations from its scope. Its main points:
- Be identifiable: publish real registrant contact data in WHOIS or RDAP, or test that the proxy forwarding works and is monitored.
- Coordinate with the brand owner: early contact prevents takedowns and disputes; one option is for the brand owner to hold the domain and point it at your nameservers.
- Avoid MX unless needed: an MX record signals email capability, worries brand owners and can be cited as evidence of bad faith in UDRP cases.
- Disclose and minimise content: state on landing pages that the domain is not used for real phishing, do not include username or password fields, prefer neutral "you clicked a simulated link" pages, and restrict access to the relevant networks.
- Expect blocking: arrange mail gateway exceptions and DNS and firewall entries before an exercise, and assume reputation blocklists may list the domain.
- Clean up: after the exercise, remove the site and stop the domain resolving.
The document notes that UDRP panels have reached different results in anti-phishing training cases and that it is not legal advice.
Where identity fits
Registrar and DNS provider accounts are some of the most powerful identities you have: whoever controls them can redirect email, sign-in pages and API endpoints and obtain certificates for your names. Many are also used by automation through API keys, for example certificate issuance clients that create DNS validation records or infrastructure-as-code pipelines that manage zones. Scope those keys to the zones and record types they need, store them in a secrets manager, and alert on their use outside the pipeline. Domains also anchor non-human trust: OAuth redirect URIs, webhook endpoints and SAML entity IDs all reference domains, so retiring a domain must include removing those references first. See the API Key Management Guide.
Retiring domains safely
- Search for references: allowlists, content security policies, OAuth redirect URIs, webhooks, email routing rules, hard-coded links in documents and code, and DNS CNAMEs pointing at the domain.
- Remove references and dangling records first: the NCSC warns that unused delegations and CNAMEs can enable subdomain takeover.
- Hold before release: keep high-traffic or long-used domains registered with non-sending email records for a holding period (often several years) so misdirected email and links fail safely.
- Decide explicitly: release only low-risk domains, recorded with an approver, never by letting a card expire.
Detection and measurement
- Percentage of domains in organisational registrar accounts with MFA and registrar lock (target 100 percent).
- Number of domains expiring in the next 60 days without auto-renew (target zero).
- Percentage of non-sending domains with SPF
-all, DMARC reject, null DKIM and null MX. - Median time from detection of a malicious lookalike to blocklisting internally and to takedown request.
- Number of active lookalikes with MX records or valid certificates per month, and the trend.
- Unexpected DNS or certificate events on Tier 1 domains investigated within one business day.
Common failure patterns
- Domains on personal cards or agency accounts: the renewal fails when the person leaves or the agency relationship ends, and the domain lapses.
- Letting an old domain expire: references in allowlists and email survive the domain, which is exactly how the expired domain in the ForcedLeak research became trusted infrastructure for whoever bought it.
- Parked domains with no email records: attackers spoof your genuine but unused domains because nothing tells receivers to reject the mail.
- Buying hundreds of variants and monitoring none: budget goes on long-tail registrations while the one convincing lookalike used against finance staff is registered in an unmonitored TLD. See the Business Email Compromise Awareness for Finance Teams Guide.
- Registrar accounts without MFA: a single phished password gives control of nameservers and therefore email and certificates.
- Security simulations that become complaints: lookalikes registered for phishing tests without contact data, disclosure or clean-up, which then get reported, blocklisted or disputed.
Framework mapping
| Framework | Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | ID.AM-02; ID.AM-08; PR.AA-01; DE.AE-07 | Inventory of services, lifecycle management, managing account identities, integrating threat intelligence |
| NIST SP 800-53 Rev. 5 | CM-8 System Component Inventory; SI-4 System Monitoring; PM-16 Threat Awareness Program | Domain inventory, DNS and certificate monitoring, lookalike intelligence |
| IETF | RFC 7505 Null MX | Declaring that a domain accepts no mail |
| ICANN | UDRP paragraphs 4(a), 4(b), 4(i); URS | Dispute routes |
| MITRE ATT&CK v20 | T1583.001; T1584.001; T1566.002 | Adversary acquisition and compromise of domains, link phishing |
Practitioner checklist
- Build a complete domain inventory with owner, backup owner, registrar, expiry, email use and tier.
- Consolidate domains into organisational registrar accounts with MFA for every administrator.
- Enable registrar lock on all domains and registry lock on Tier 1 domains.
- Set auto-renew on an organisational payment method and alert 60 days before any expiry.
- Publish null SPF, DMARC reject, null DKIM and null MX on every non-sending domain.
- Monitor DNS record changes and certificate transparency for your domains and brand names.
- Run permutation scanning and triage lookalikes by MX, certificate and content.
- Agree takedown routes, evidence standards and counsel contacts before you need them.
- Follow the M3AAWG practices for any lookalike your security team registers for testing.
- Retire domains only after removing references and dangling DNS, with a holding period.
Standards and references
- M3AAWG: Best Practices for Use of Look-Alike Domains for Security Purposes
- NCSC: Managing Public Domain Names
- GOV.UK: Protect Domains That Do Not Send Email
- IETF: RFC 7505 A Null MX No Service Resource Record
- ICANN: Uniform Domain Name Dispute Resolution Policy
- ICANN: Uniform Rapid Suspension System
- Unicode Consortium: UTS #39 Unicode Security Mechanisms
- dnstwist: Domain Name Permutation Engine
Related NHI Mgmt Group resources: Typosquatting and Lookalike Domains Guide · Brand Impersonation and Lookalike Domain Takedown Playbook · Disinformation and Brand Impersonation Guide · Authoritative DNS and Registrar Account Security Guide · Email Identity and BEC Guide