Skip to security report
Analytics Dashboard
Domain security and threat intelligence
fileoasis.net favicon

fileoasis.net

In short

fileoasis.net is a phishing page detected by PhishDestroy on 2026-10-24. Risk: critical (100/100). Registrar: Namecheap. Status: Last known active. Hosting: Amazon.com. PhishDestroy sent 1 abuse report. VirusTotal: 13/92 engines flag it. Do not enter credentials or connect a wallet.

“An Error Occurred: OK”

Review the evidence
Registrar
Namecheap
Resolved IP
23.22.126.183
Registered
Jul 19, 2016
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 13/92
Oct 24, 2026 1 Report Sent
API
This domain has been flagged as malicious
Security engines reporting a detection: 13. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
13 / 92
engine detections
URLQuery
2
detections
Page captures
8
open gallery
Domain age
3749 days
Reports sent
1
view timeline
Source evidenceVirusTotal 13 / 92 4 sources

VirusTotal

13 / 92 engine detections

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware
View full Cloudflare Radar report

Analysis

Critical
VirusTotal
13 / 92
Page captures
8
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy listed fileoasis.net as a suspicious domain based on multiple security‑engine detections. The recorded page title is “An Error Occurred: OK”. The domain was first seen by PhishDestroy on 2026-10-24 and returned HTTP 200 on that date.

How the scam works

The listing reflects a generic risk that domains flagged by many security engines often host phishing pages, malware downloads, or fraudulent content, but no specific malicious behavior was observed on the captured page. Without concrete evidence, the exact scheme cannot be determined beyond the possibility of typical web‑based fraud tactics.

Evidence

VirusTotal analysis on 2026-10-18 (retrieved 2026-10-24) recorded 13 detections: 11 malicious and 2 suspicious across 92 engines, with vendors such as ADMINUSLabs, Dr.Web, Fortinet, Kaspersky, Lionic, Sophos, Webroot, and others marking it malicious. Google Safe Browsing checked on 2026-10-24 did not flag the site. Cloudflare Radar scan on 2026-10-24 labeled the domain malicious for malware. URLScan capture on 2026-10-24 reported an overall non‑malicious verdict with a neutral score.

Infrastructure

The recorded IP was 23.22.126.183, belonging to an Amazon.com network in the United States. The domain was registered on 2016-07-19 through NameCheap, Inc. TLS is provided by a Let's Encrypt certificate valid from 2026-08-26 to 2026-11-24, covering *.fileoasis.net. Nameservers are AWS‑hosted and DNSSEC is not enabled.

What to do

Visitors should avoid entering credentials or downloading files from this site and should change any passwords used there. Administrators should block fileoasis.net at network perimeters and monitor logs for connections. Security teams can reference the PhishDestroy listing and the detailed VirusTotal and Cloudflare Radar findings when investigating related alerts.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-24T13:59:52Z)URLScan screenshot (2026-10-24T12:52:06Z)URLScan capture reportURLScan screenshot (2026-10-24T12:55:22Z)URLScan capture reportURLScan screenshot (2026-10-24T13:10:25Z)URLScan capture reportURLScan screenshot (2026-10-24T13:27:36Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Questions about fileoasis.net

Is fileoasis.net legit?

No. PhishDestroy classifies fileoasis.net as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-24. VirusTotal: 13/92 engines flag it. Treat the site as unsafe.

Is fileoasis.net safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on fileoasis.net. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used fileoasis.net?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 8 captures

Primary capture 1 / 8
SourcePrimary capture
Recorded2026-10-24 13:59 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://fileoasis.net/
Position1 / 8
Open capture Wayback Download

Domain details

Domain
IP Reputation abuse score 0/100 0 reports checked Oct 24, 2026
Registrar Namecheap US(US)
Abuse contactabuse@namecheap.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for fileoasis.net →
RegistrationCreated Jul 19, 2016 — Expires Jul 19, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 24, 2026
DOM Analysisanalyzed Oct 24, 2026score 88/100
Submitted URLhttps://fileoasis.net/
Case ID
Observed page title
An Error Occurred: OK
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 30 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
23.22.126.183
Network ASN
AS14618
Organization
Amazon.com
Observed location
Ashburn, US
Server header
nginx

Nameservers 4

  • ns-1062.awsdns-04.org
  • ns-1568.awsdns-04.co.uk
  • ns-203.awsdns-25.com
  • ns-858.awsdns-43.net

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-08-26 14:08:56
Valid until
2026-11-24 14:08:55
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint21a0e15b67b6291c38109febce2ace67f51fd493f003dcba790fd14ba0a7a094
Certificate names · 2 SANs
  • *.fileoasis.net
  • fileoasis.net

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 23.22.126.183rapiddns.io
Recorded subdomains3

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • cdn.fileoasis.netDomain record
  • cdn.staging.fileoasis.netDomain record
  • www.fileoasis.netDomain record

The original observation time is not recorded for these hostnames.

Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

13 / 92 security vendors flagged this domain
View on VT
Last analyzed
ADMINUSLabs
alphaMountain.ai
Dr.Web
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
Kaspersky
Lionic
SafeToOpen
Seclookup
Sophos
URLQuery
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of fileoasis.net · checked Oct 24, 2026

100
Good
Performance
FCP
0.8 s
First Contentful Paint
LCP
0.8 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
0.83 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://fileoasis.net/
An Error Occurred: OK
Response
HTTP 200
HTML body
979 B
Compressed
631 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html; charset=utf-8
Cache-Control: no-cache, private
Content-Encoding: gzip
Security headers present
Strict-Transport-SecurityX-Content-Type-OptionsX-XSS-Protection
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 12
Cache-Control
no-cache, private
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sat, 24 Oct 2026 14:00:46 GMT
Server
nginx
Strict-Transport-Security
max-age=31536000; includeSubDomains
Transfer-Encoding
chunked
Vary
Accept-Encoding
X-Content-Type-Options
DENY
x-robots-tag
none
X-XSS-Protection
1; mode=block

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
URLScan · 2026-10-24T13:58:44Z

Observed: · Retrieved:

Uuid
01a16e34-d503-711c-982f-eeb9f9f3ff79
Final url
https://fileoasis.net/
Status
200
Ip
23.22.126.183
Ptr
ec2-23-22-126-183.compute-1.amazonaws.com
Contacted IP addresses
[
    "23.22.126.183"
]
Asns
[
    "14618"
]
Countries
[
    "US"
]
Document hash
d5fd9a63e43c5fb7260b6923a74261394d8409ae1685db9c2735baffc9bfc4e5
Cookies
[
    "XSRF-TOKEN",
    "tool_session"
]
Tls
{
    "san": [
        "*.fileoasis.net",
        "fileoasis.net"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "fileoasis.net",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-24T14:08:55Z",
    "valid_from": "2026-08-26T14:08:56Z"
}
Domain age days
3747
Apex age days
3747
Tls age days
58
Tls valid days
89
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -83,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains",
    "x-content-type-options": "DENY\nnosniff"
}
Cloudflare Radar · 2026-10-24T13:59:52Z

Observed: · Retrieved:

Uuid
58fa0a21-6722-48dc-b8db-bf76a3309dba
Final url
https://fileoasis.net/
Status
200
History
[
    {
        "url": "https://fileoasis.net/",
        "status": 200
    }
]
DOM structure hash
942dad6c2187cf849ddded8f9defeae37e5c1346f2826c8880453dc2181f6c96
Document hash
d5fd9a63e43c5fb7260b6923a74261394d8409ae1685db9c2735baffc9bfc4e5
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "fileoasis.net",
        "type": "A",
        "value": "23.22.126.183"
    }
]
Dnssec valid
false
Ip
23.22.126.183
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "NameCheap, Inc.",
    "created": "2016-07-19T16:58:46Z",
    "updated": "2026-07-19T20:56:46Z",
    "expires": "2027-07-19T16:58:46Z",
    "nameservers": [
        "ns-1062.awsdns-04.org",
        "ns-1568.awsdns-04.co.uk",
        "ns-203.awsdns-25.com",
        "ns-858.awsdns-43.net"
    ]
}
VirusTotal · 2026-10-18T09:10:39Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 48,
    "malicious": 11,
    "suspicious": 2,
    "undetected": 31
}
Vendor labels
{
    "Dr.Web": "malicious",
    "Lionic": "malicious",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "URLQuery": "suspicious",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "SafeToOpen": "phishing",
    "ADMINUSLabs": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Dr.Web": "known infection source",
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "BitDefender": "adsnetwork"
}
Popularity
{
    "Alexa": 552827,
    "Statvoo": 552827,
    "Quantcast": 122116,
    "Cisco Umbrella": 667918
}
Registrar
NAMECHEAP INC
Created
2016-07-19T16:58:46Z
Expires
2027-07-19T16:58:46Z
Updated
2026-07-19T20:56:46Z
First seen
2023-09-28T17:40:16Z
DNS records
[
    {
        "ttl": 900,
        "type": "SOA",
        "rname": "awsdns-hostmaster.amazon.com",
        "value": "ns-1568.awsdns-04.co.uk"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns-858.awsdns-43.net"
    },
    {
        "ttl": 60,
        "type": "A",
        "value": "23.22.126.183"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns-1062.awsdns-04.org"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns-203.awsdns-25.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns-1568.awsdns-04.co.uk"
    }
]
Dns at
2026-10-18T09:10:53Z
Jarm
27d40d40d00040d00042d43d000000e1ea2a807a629b496b664cf07ad7c08d
Certificate
{
    "san": [
        "*.fileoasis.net",
        "fileoasis.net"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "52698c2361a5d84fb24c5548dda9e4eb1dc",
    "sha256": "21a0e15b67b6291c38109febce2ace67f51fd493f003dcba790fd14ba0a7a094",
    "subject": "fileoasis.net",
    "valid_to": "2026-11-24T14:08:55Z",
    "valid_from": "2026-08-26T14:08:56Z"
}
Registration record
{
    "registrar": "NAMECHEAP INC",
    "registrar_iana_id": "1068",
    "registrar_url": "http://www.namecheap.com",
    "created": "2016-07-19T16:58:46Z",
    "updated": "2026-07-19T20:56:46Z",
    "expires": "2027-07-19T16:58:46Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns-1062.awsdns-04.org",
        "ns-1568.awsdns-04.co.uk",
        "ns-203.awsdns-25.com",
        "ns-858.awsdns-43.net"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "last changed": "2026-07-19T20:56:46Z",
        "registration": "2016-07-19T16:58:46Z",
        "registrar expiration": "2027-07-19T16:58:46Z",
        "last update of RDAP database": "2026-10-17T23:25:45Z"
    }
}
Website checks · 2026-10-24T14:00:19Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "fileoasis.net"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2025-07-14T20:48:09Z",
    "first": "2017-05-27T04:01:32Z",
    "changes": 57,
    "days_archived": 77,
    "scans_per_day": 0.03,
    "avg_page_bytes": 7641
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "An Error Occurred: OK",
    "robots": "noindex,nofollow,noarchive"
}
Trackers
{
    "requests": 0
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 23,
        "tls": 122,
        "wait": 131,
        "connect": 102,
        "download": 0
    },
    "response_ms": 378
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 979,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "205.251.196.38",
            "host": "ns-1062.awsdns-04.org"
        },
        {
            "ip": "205.251.198.32",
            "host": "ns-1568.awsdns-04.co.uk"
        },
        {
            "ip": "205.251.192.203",
            "host": "ns-203.awsdns-25.com"
        },
        {
            "ip": "205.251.195.90",
            "host": "ns-858.awsdns-43.net"
        }
    ],
    "zone": "fileoasis.net"
}
Cookies
{
    "cookies": [
        {
            "name": "XSRF-TOKEN",
            "secure": true,
            "same_site": "Lax"
        },
        {
            "name": "tool_session",
            "secure": true,
            "http_only": true,
            "same_site": "Lax"
        }
    ]
}
Location
{
    "ip": "23.22.126.183",
    "asn": "14618",
    "org": "Amazon.com",
    "city": "Ashburn",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "fileoasis.net"
}
DNS records
{
    "A": [
        "23.22.126.183"
    ],
    "NS": [
        "ns-858.awsdns-43.net",
        "ns-203.awsdns-25.com",
        "ns-1062.awsdns-04.org",
        "ns-1568.awsdns-04.co.uk"
    ],
    "SOA": "{\"nsname\": \"ns-1568.awsdns-04.co.uk\", \"hostmaster\": \"awsdns-hostmaster.amazon.com\", \"serial\": 1, \"refresh\": 7200, \"retry\": 900, \"expire\": 1209600, \"minttl\": 86400}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000; includeSubDomains",
    "message": "HSTS header does not contain the preload directive."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": "1; mode=block, 1; mode=block",
    "permissionsPolicy": false,
    "xContentTypeOptions": "DENY, nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31536000; includeSubDomains",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "23.22.126.183",
    "family": 4
}
Redirects
{
    "chain": [
        "https://fileoasis.net"
    ]
}
Registration record
{
    "registrar": "NameCheap, Inc.",
    "created": "2016-07-19T16:58:46Z",
    "updated": "2026-07-19T20:56:46Z",
    "expires": "2027-07-19T16:58:46Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns-1062.awsdns-04.org",
        "ns-1568.awsdns-04.co.uk",
        "ns-203.awsdns-25.com",
        "ns-858.awsdns-43.net"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=31536000; includeSubDomains",
        "x-content-type-options": "DENY, nosniff"
    }
}
Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. Abuse report sent

    PD-20261024-30D034

    abuse@namecheap.com
  2. Wayback Machine

    Page archived

    View source
  3. VirusTotal

    13/92 engine detections

    View source
  4. Added to PhishDestroy

    fileoasis.net

    View source
  5. URLScan

    Page captured

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

fileoasis.net

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 13 det. ChainPatrol URLQuery 2 det. SSL Labs Stored certificate dates valid CF Radar Malicious WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261024-30D034 Recipient: abuse@namecheap.com
Page title stored with report: An Error Occurred: OK
PDF notice generated Notice text archived (289 chars)
Abuse notice text as sent to the provider 
Registrar: Namecheap Inc (United States)
Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Last known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 fileoasis.net)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/fileoasis.net"
  title="PhishDestroy threat report for fileoasis.net"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>