public company · US

NatWest Group plc

Primary official domain
natwestgroup.com
Reviewed official domains
1 (directory review; organization has not verified)
Directory source
BreachScout directory · Suggest a correction
Matching domains, 30 days
2
registrable domains containing the brand; source date or last feed observation
First source-reported, 30 days
0
domains first source-reported within 30 days
First observed, 30 days
2
domains first observed by DomainSpoof in feeds
Email policy (primary domain)
DMARC reject
SPF -all · 0/10 lookups · Mail: Receives mail (2 MX hosts) · checked 2026-10-20 · published policy

What we watch for

Hostnames in phishing feeds and certificate logs are matched on these brand tokens; feed target labels are matched on the aliases. Generated spellings (typos, lure words, look-alike characters, other top-level domains) are derived from the official domains and tokens and checked against feeds, certificate logs and DNS.

Brand tokens
natwest
Label aliases
NatWest Group plc · NatWest Bank
Official domains
natwestgroup.com (all)
Generated spellings
237 tracked · 37 observed somewhere · 200 not observed (all)
Can receive mail
20 spellings and 1 reported domain publish MX records · mail at Above.com parking (parking placeholder) 8 · mailerhost.net (parking placeholder) 3 · CSC (corporate registrar) 1 · 9 more (37 spellings and 2 reported domains of the last 30 days checked; MX shows the domain can receive mail, not who operates it)

Official domains and email policies

Domains reviewed as belonging to NatWest Group plc. DMARC helps receivers check the From domain; lookalike domains remain possible. Published policies cannot confirm actual mail configuration or receiver behavior.

DomainRelationshipEvidenceDMARC policyPolicy sourceSPFReportingMailDKIMMTA-STSLast check
natwestgroup.com
primaryReviewed —
Portfolio directory (financedb_ticker_A)rejectDirect-all · 0/10 lookupsAggregate reports requested (rua)Receives mail (2 MX hosts)Unknown (no key at common selectors)
No MTA-STSNo TLS-RPT
2026-10-20 03:07 UTC
Records and check details

Published records

DMARC (_dmarc.natwestgroup.com)
v=DMARC1; p=reject; fo=1; rua=mailto:…@rua.netcraft.com; ruf=mailto:…@ruf.netcraft.com
SPF (natwestgroup.com)
v=spf1 ip4:155.136.80.0/24 -all
MX (natwestgroup.com)
10 relay1.netnames.net · 100 relay2.netnames.net
DKIM
Unknown (no key at common selectors). DKIM use requires a known selector or message to assess; a published key alone cannot confirm signing, and no key at the probed common selectors proves nothing.
MTA-STS (_mta-sts.natwestgroup.com)
No MTA-STS
TLS-RPT (_smtp._tls.natwestgroup.com)
No TLS-RPT

Interpretation

  • p=reject: receivers are asked to reject failing mail.
  • Relaxed DKIM alignment (default).
  • Relaxed SPF alignment (default).
  • -all: unlisted hosts fail SPF.
  • 0 DNS-querying terms (include, a, mx, ptr, exists, redirect), counted recursively; the limit is 10.
  • Static check of the published record: syntax, every referenced include/redirect record, the DNS-lookup count and a/mx/exists targets (resolved to count void lookups). It does not evaluate SPF for any particular sending host.
  • Receives mail (2 MX hosts).
  • No usable DKIM key at the 28 common selectors probed. DKIM may use other selectors, so this proves nothing about DKIM use.
  • No MTA-STS record (_mta-sts TXT).
  • No TLS-RPT record: no address for SMTP TLS failure reports, a visibility gap rather than an enforcement setting.

DMARC discovery (RFC 9989 tree walk)

  1. _dmarc.natwestgroup.com: ok, 1 DMARC record

Recent checks

  • 2026-10-20 03:07 UTC: DMARC reject; SPF -all; 2 MX hosts; no MTA-STS
  • 2026-10-19 00:41 UTC: DMARC reject; SPF -all

Assessment posture-v3. DNS lookup failures leave the policy unknown.

“Not checked”: no check yet (mail, DKIM and MTA-STS facts were added later, so older checks show “Not checked” for them). “Lookup failed”: DNS result unknown. DKIM is probed at a fixed list of common selectors only. Report mailbox names are redacted.

Reports on official domains appear under “Official assets with reports” on the Reported matches tab.