public company · US

BARCLAYS BANK PLC

Primary official domain
Not yet assessed
Reviewed official domains
0 (directory review; organization has not verified)
Directory source
BreachScout directory · Suggest a correction
Matching domains, 30 days
5
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
5
domains first observed by DomainSpoof in feeds
Email policy (primary domain)
Not checked
No email-policy check yet

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
barclays
Label aliases
Barclays
Official domains
None recorded (all)
Generated spellings
109 tracked · 38 observed somewhere · 71 not observed (all)
Can receive mail
19 spellings and 4 reported domains publish MX records · mail at CSC (corporate registrar) 8 · Google 4 · Above.com parking (parking placeholder) 2 · 9 more (38 spellings and 5 reported domains of the last 30 days checked; MX shows the domain can receive mail, not who operates it)

Matching domains with source reports or listings

Source claims are shown separately from our company matches. Default scope: brand in hostname. Choose “All associations” to include source-labelled matches on other sites.

Domain / hostnameSource claimCompany match (DomainSpoof)Date (mixed basis)Latest DNSSources / recordsFinding details
barclaysfinancelimited[.]comMail: DMARC · checked 2026-10-19DMARC policy quarantine
Listed by PhishDestroyPresent in latest snapshot
Possible associationBrand in hostname
2026-10-20Observed in feed
Alive13.248.213.45Amazon Web ServicesAmazon Web Services (AS16509) · USa67c48129651a0940.awsglobalaccelerator.com76.223.67.189Amazon Web ServicesAmazon Web Services (AS16509) · USa67c48129651a0940.awsglobalaccelerator.comchecked 2026-10-19 23:00 UTC
1 source · 1 recordDetails
barclayswealthservices[.]comMail: MXSPFDMARC · checked 2026-10-19mail at mx1.1984.is · DMARC policy none (monitor only) · sends via _spf.1984.is
Listed by PhishDestroyPresent in latest snapshot
Possible associationBrand in hostname
2026-10-20Observed in feed
Alive185.112.145.243 · Confirmed phishing host address (DomainSpoof, 48 hours)THE-1984-AS (AS44925) · ISgeorge.shared.1984.ischecked 2026-10-19 23:00 UTC
1 source · 1 recordDetails
barclays-grads[.]twineapp[.]comMail: MXSPF · checked 2026-10-19mail at Google (consumer mailbox) · sends via Google, SendGrid, Mailchimp
Listed by PhishDestroyPresent in latest snapshot
Possible associationBrand in hostname
2026-10-20Observed in feed
Alive52.51.42.11Amazon Web ServicesAmazon Web Services (AS16509) · USec2-52-51-42-11.eu-west-1.compute.amazonaws.com54.75.94.216Amazon Web ServicesAmazon Web Services (AS16509) · USec2-54-75-94-216.eu-west-1.compute.amazonaws.comchecked 2026-10-19 23:00 UTC
1 source · 1 recordDetails
barclays-grads[.]twinehr[.]comMail: MX · checked 2026-10-19mail at Google (consumer mailbox)
Listed by PhishDestroyPresent in latest snapshot
Possible associationBrand in hostname
2026-10-20Observed in feed
Alive52.51.42.11Amazon Web ServicesAmazon Web Services (AS16509) · USec2-52-51-42-11.eu-west-1.compute.amazonaws.com54.75.94.216Amazon Web ServicesAmazon Web Services (AS16509) · USec2-54-75-94-216.eu-west-1.compute.amazonaws.comchecked 2026-10-19 23:00 UTC
1 source · 1 recordDetails
westbarclays-bnkplc[.]com[.]trMail: MX · Confirmed phishing host address (DomainSpoof, 48 hours)SPF · Confirmed phishing host address (DomainSpoof, 48 hours) · checked 2026-10-19mail at mail.westbarclays-bnkplc.com.tr
Listed by PhishDestroyPresent in latest snapshot
Possible associationBrand in hostname
2026-10-20Observed in feed
Alive198.251.83.49 · Confirmed phishing host address (DomainSpoof, 48 hours)PONYNET (AS53667) · USd2mail49.my-control-panel.comchecked 2026-10-19 23:00 UTC
1 source · 1 recordDetails

A feed listing or DNS answer alone cannot confirm current phishing. Removal from a feed does not confirm resolution.