PhishDestroy first recorded web.natwestaccessfinance.com on 2026-08-30. Stored VirusTotal result: 12/92 engines flagged. Malicious: 11. Suspicious: 1. Analysis time (as stored): 2026-10-12 04:02 UTC. Retrieved (as stored): 2026-10-23 11:37 UTC.
Page title: “Natwestaccessfinance”
More about the sources
Recorded security signals
Stored VirusTotal result: 12/92 engines flagged. Malicious: 11. Suspicious: 1. Analysis time (as stored): 2026-10-12 04:02 UTC. Retrieved (as stored): 2026-10-23 11:37 UTC. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded web.natwestaccessfinance.com on 2026-08-30. Stored VirusTotal result: 12/92 engines flagged. Malicious: 11. Suspicious: 1. Analysis time (as stored): 2026-10-12 04:02 UTC. Retrieved (as stored): 2026-10-23 11:37 UTC. Risk: critical (evidence score 90/100). Registrar: Realtime. Status: Content unavailable. Hosting: Ultahost, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
web.natwestaccessfinance.com is an impersonation phishing page posing as NatWest under the title "Natwestaccessfinance." It targets NatWest customers and anyone looking for finance from the bank. PhishDestroy first flagged it on 2026-08-30. The site has been offline since 2026-09-11, and on 2026-10-19 its DNS was still inactive.
How the scam works
The page title and the domain both combine the NatWest name with "access finance" to look like an official bank or lending portal. Victims typically arrive through a text, email or ad and see a login or application screen. That screen captures customer numbers, passwords, PINs, one-time codes and personal details. The attackers use them to sign in to the real account, move money or approve payments before the victim notices.
Evidence
Ten of 91 VirusTotal engines flagged the domain when it was checked on 2026-08-31. The engines that flagged it include alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. These are separate vendors, so their agreement supports the phishing verdict independently of our own classification. Spamhaus lists the domain on its DBL as a phishing domain, and it is on the PhishDestroy blocklist.
Infrastructure
The domain was registered on 2026-05-20 through Realtime Register B.V., about three months before we detected it. That gap suggests the name was held in reserve before the campaign went live. The site was hosted on Ultahost, Inc. in the Netherlands, which has no connection to a UK bank. Its free Let's Encrypt certificate gave it a padlock icon, which proves nothing about who runs a site.
What to do
If you entered NatWest login details here, contact NatWest right away using the number on your card or the official app. Change your password and PIN, and ask the bank to review recent payments and payees. If you shared one-time codes or card details, tell the bank so it can block the card and watch for fraudulent transfers. Report the message that sent you to the page to your provider and the bank. Defenders should block the domain and look for similar "natwest" lookalike names registered around the same time.
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
web.natwestaccessfinance.com was a phishing page impersonating NatWest, built to steal online banking logins and personal data from UK bank customers.
AI summary
Overview web.natwestaccessfinance.com is an impersonation phishing page posing as NatWest under the title "Natwestaccessfinance." It targets NatWest customers and anyone looking for finance from the bank. PhishDestroy first flagged it on 2026-08-30. The site has been offline since 2026-09-11, and on 2026-10-19 its DNS was still inactive. How the scam works The page title and the domain both combine the NatWest name with "access finance" to look like an official bank or lending portal. Victims typically arrive through a text, email or ad and see a login or application screen. That screen captures customer numbers, passwords, PINs, one-time codes and personal details. The attackers use them to sign in to the real account, move money or approve payments before the victim notices. Evidence Ten of 91 VirusTotal engines flagged the domain when it was checked on 2026-08-31. The engines that flagged it include alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. These are separate vendors, so their agreement supports the phishing verdict independently of our own classification. Spamhaus lists the domain on its DBL as a phishing domain, and it is on the PhishDestroy blocklist. Infrastructure The domain was registered on 2026-05-20 through Realtime Register B.V., about three months before we detected it. That gap suggests the name was held in reserve before the campaign went live. The site was hosted on Ultahost, Inc. in the Netherlands, which has no connection to a UK bank. Its free Let's Encrypt certificate gave it a padlock icon, which proves nothing about who runs a site. What to do If you entered NatWest login details here, contact NatWest right away using the number on your card or the official app. Change your password and PIN, and ask the bank to review recent payments and payees. If you shared one-time codes or card details, tell the bank so it can block the card and watch for fraudulent transfers. Report the message that sent you to the page to your provider and the bank. Defenders should block the domain and look for similar "natwest" lookalike names registered around the same time. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a0506e-932d-77a2-b577-109ab23cce8e/ VirusTotal report: https://www.virustotal.com/gui/domain/web.natwestaccessfinance.com Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=web.natwestaccessfinance.com Archived copy: https://web.archive.org/web/20260830021415/https://web.natwestaccessfinance.com/ Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
PhishDestroy rates web.natwestaccessfinance.com as critical risk (evidence score 90/100) from the recorded evidence; it was first recorded on 2026-08-30. Stored VirusTotal result: 12/92 engines flagged. Malicious: 11. Suspicious: 1. Analysis time (as stored): 2026-10-12 04:02 UTC. Retrieved (as stored): 2026-10-23 11:37 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is web.natwestaccessfinance.com safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on web.natwestaccessfinance.com. A confirmed blockchain transaction cannot be reversed.
What should I do if I used web.natwestaccessfinance.com?
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Downloaded a file — do not open it and scan the device with security software
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
IP Reputation109.176.207.2220/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worseThis IP address has a low abuse score, but the domain itself is recognized as phishing.0 reportschecked 2026-08-30last reported · outside the counted period
Registration (base domain)natwestaccessfinance.com · Created 2026-05-20 (185d)—Expires 2027-05-20
Time to First Unavailability12 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First Detected2026-08-30
Submitted URLhttp://web.natwestaccessfinance.com/
Favicon Hash
Case ID
Observed page title
Natwestaccessfinance
TLS Certificate
Issued by Let's Encrypt· stored validity ends in 78 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
109.176.207.222
Network ASN
AS214036
Organization
Ultahost, Inc.
Observed location
Amsterdam, NL
Server header
LiteSpeed
Nameservers 2
ns1.meetabee.com
ns2.meetabee.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid from
2026-08-19 08:10:08
Valid until
2026-11-17 08:10:07
Hostname match
Yes
Validity
Stored certificate expired
Collection time
2026-08-30 04:02 UTC
Collection source
PhishDestroy collector
Certificate fingerprint19e5e957b9976f4e612daa6f0554a77d37e7bc075475d34b357b84913fdb7faeCertificate names · 2 SANs
web.natwestaccessfinance.com
www.web.natwestaccessfinance.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAIN
RDAP registration
Observed timelinelast reachable: 2026-09-04 22:16 UTCcurrent episode first observed: 2026-09-30 16:14 UTCobserved RIP window: 2026-09-04 22:16 UTC → 2026-09-30 16:14 UTC · 617.98hmidpoint estimate ≈ 2026-09-17 19:15 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 02:56 UTC.
Recorded events: 16. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Time to First Unavailability
Hours from detection to the first unavailable observation: 283
Recorded activity
6 entries
Lifecycle
Domain registered
Added to PhishDestroy+101 d 3 h
First abuse report sent+4 min
VirusTotal analysis with detections+43 d 1 h
Reported 101 d 3 h after registration
VirusTotal
12/92 engine detections
+43 d 1 h
Realtime Register
Asked for a report through its web form
same minute
Abuse report sent
PD-20260830-9560EB · Receipt 63853
rtr-security-threats@realtimeregister.com
+2 min
Wayback Machine
Page archived
+2 min
Added to PhishDestroy
web.natwestaccessfinance.com
same minute
URLScan
Page captured
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Shared IP 109.176.207.2226
Multiple reports share this IP.
Other PhishDestroy reports on this IP address: 16Shown below: the 6 with the most VirusTotal detections.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including web.natwestaccessfinance.com)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.