Skip to security report
Analytics Dashboard
Domain security and threat intelligence
dfsfiles.com favicon

dfsfiles.com

In short

dfsfiles.com is a phishing page detected by PhishDestroy on 2026-10-25.

“Etab Management System”

Review the evidence
Registrar
GoDaddy
Resolved IP
69.167.176.86
Registered
Jul 29, 2009
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 6/92
VirusTotal
6 / 92
engine detections
OTX
0
community references
Cloudflare Radar
clean
source verdict
Page captures
8
open gallery
Domain age
6296 days
Reports sent
1
view timeline
Oct 25, 2026 1 Report Sent
API
This domain has been flagged as malicious
Security engines reporting a detection: 6. Exercise extreme caution — do not enter credentials or personal information.

Analysis

Domain summary

dfsfiles.com is a phishing page detected by PhishDestroy on 2026-10-25. Risk: critical (82/100). Registrar: GoDaddy. Status: Last known active. Hosting: Liquid Web, L.L.C. PhishDestroy sent 1 abuse report. VirusTotal: 6/92 engines flag it. Do not enter credentials or connect a wallet.

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

PhishDestroy threat report

Overview

PhishDestroy added dfsfiles.com to its internal blocklist on 2026-10-25 after intake flagged the domain because six VirusTotal scanners reported it as malicious. The recorded page title is "Etab Management System" and the HTTP response was 200 on the same date. Google Safe Browsing did not flag the domain and no external blocklists reported it as malicious at the time of checking.

How the scam works

A domain that triggers multiple antivirus detections is often used to host phishing pages, deliver malware, or impersonate legitimate services, but the current evidence does not show a specific payload or credential‑harvesting form. In general, such sites may lure visitors into entering login details or downloading files that compromise their system. Without observed malicious forms on dfsfiles.com, we can only note the generic risk associated with domains flagged by several security engines.

Evidence

VirusTotal (2026-10-25) listed six malicious detections from BitDefender, CRDF, G-Data, Gridinsoft, SOCRadar and VIPRE out of 92 engines. Google Safe Browsing (2026-10-25) reported no threat. urlscan.io (2026-10-25) returned a clean verdict with no malicious tags and a simple HTTPS redirect. OTX showed zero pulses. PhishDestroy’s internal list marks the domain as blocked, while external blocklists returned zero hits.

Infrastructure

The domain was registered on 2009-07-29 through GoDaddy.com, LLC and is hosted on IP 69.167.176.86, a Liquid Web, L.L.C network in the United States. TLS 1.3 is used with a GoDaddy DV certificate valid until 2027-04-23; the SAN list also contains unrelated domains. DNS records show standard A, MX, NS and TXT entries, no DNSSEC, and open ports 25, 80, 110, 143, 443, 587.

What to do

Visitors should avoid entering any credentials or downloading files from dfsfiles.com and, if they have already done so, change passwords on any related accounts. Security teams should block the domain, monitor outbound traffic for connections to 69.167.176.86, and log any attempts to access the site for further investigation.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-25T06:23:25Z)URLScan screenshot (2026-10-18T01:11:10Z)URLScan capture reportURLScan screenshot (2026-10-18T14:51:19Z)URLScan capture reportURLScan screenshot (2026-10-20T06:11:15Z)URLScan capture reportURLScan screenshot (2026-10-22T11:11:02Z)URLScan capture reportURLScan screenshot (2026-10-25T03:21:00Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 6 / 92 6 sources

VirusTotal

6 / 92 engine detections

Open report
VirusTotal · 2026-10-25T00:30:17Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 6,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "CRDF": "malicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "SOCRadar": "phishing",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing"
}
Reputation
0
Registrar
GoDaddy.com, LLC
Created
2009-07-29T23:11:55Z
Expires
2027-07-29T23:11:55Z
Updated
2024-07-30T22:15:32Z
First seen
2023-10-18T00:06:49Z
DNS records
[
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "google-site-verification=iAFrdQgIpeoFZGY2WT_cCfeKP1fs650YK2WGkZ0ROc8"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns48.domaincontrol.com"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "dns.jomax.net",
        "value": "ns47.domaincontrol.com"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "69.167.176.86"
    },
    {
        "ttl": 3600,
        "type": "MX",
        "value": "dfsfiles.com",
        "priority": 10
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "v=spf1 a:host.dfsfiles.com ip4:69.167.176.86 include:_spf.google.com include:_spf.internode.on.net mx ~all"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns47.domaincontrol.com"
    }
]
Dns at
2026-10-25T00:35:39Z
Jarm
2ad2ad16d00000022c42d00000042d8c38c6b2473d2d1173e2537be3ea41ad
Certificate
{
    "san": [
        "www.dfsfiles.com",
        "dfsfiles.com",
        "www.everyrace.com.au",
        "www.everyrace.com",
        "everyrace.com"
    ],
    "issuer": "GoDaddy.com / GoDaddy TLS Intermediate CA DV - R1v1",
    "serial": "7f3b51066fcc64f5",
    "sha256": "2efbfbd5528db7d07be18d6c84b369723a43ba969e7acd63c000f4c70f714ead",
    "subject": "www.dfsfiles.com",
    "valid_to": "2027-04-23T22:51:45Z",
    "valid_from": "2026-10-07T22:51:45Z"
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "registrar_iana_id": "146",
    "registrar_url": "http://www.godaddy.com",
    "created": "2009-07-29T23:11:55Z",
    "updated": "2024-07-30T22:15:32Z",
    "expires": "2027-07-29T23:11:55Z",
    "status": [
        "clientDeleteProhibited",
        "clientRenewProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns47.domaincontrol.com",
        "ns48.domaincontrol.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client renew prohibited",
        "client transfer prohibited",
        "client update prohibited"
    ],
    "events": {
        "expiration": "2027-07-29T23:11:55Z",
        "last changed": "2024-07-30T22:15:32Z",
        "registration": "2009-07-29T23:11:55Z",
        "last update of RDAP database": "2026-10-24T04:21:05Z"
    }
}

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Not recorded
Open report
Cloudflare Radar · 2026-10-25T06:23:25Z

Observed: · Retrieved:

Uuid
deec24c4-9815-45fc-80b0-2705f9e78a95
Final url
https://dfsfiles.com/
Status
200
History
[
    {
        "url": "https://dfsfiles.com/",
        "status": 200
    }
]
DOM structure hash
43f0ef46af5466f893b016860ff480ddce2314e0f3e5379f370611ace750788f
Document hash
0221b49a736fc0a146d371e87f8e521afd463c57a744463670d7bad21899cac7
Domain risks
[
    "Travel",
    "Technology"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "dfsfiles.com",
        "type": "A",
        "value": "69.167.176.86"
    }
]
Dnssec valid
false
Ip
69.167.176.86
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "created": "2009-07-29T23:11:55Z",
    "updated": "2024-07-30T22:15:32Z",
    "expires": "2027-07-29T23:11:55Z",
    "nameservers": [
        "ns47.domaincontrol.com",
        "ns48.domaincontrol.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

URLScan

Page capture

Open report
URLScan · 2026-10-25T06:36:18Z

Observed: · Retrieved:

Uuid
01a171c6-2333-73c6-96a6-9c981b1e59ea
Final url
https://dfsfiles.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://dfsfiles.com/",
        "from": "http://dfsfiles.com/",
        "status": 307
    }
]
Ip
69.167.176.86
Ptr
host.dfsfiles.com
Contacted IP addresses
[
    "69.167.176.86"
]
Asns
[
    "32244"
]
Countries
[
    "US"
]
Document hash
0221b49a736fc0a146d371e87f8e521afd463c57a744463670d7bad21899cac7
Tls
{
    "san": [
        "www.dfsfiles.com",
        "dfsfiles.com",
        "www.everyrace.com.au",
        "www.everyrace.com",
        "everyrace.com"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "GoDaddy TLS Intermediate CA DV - R1v1",
    "subject": "www.dfsfiles.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-04-23T22:51:45Z",
    "valid_from": "2026-10-07T22:51:45Z"
}
Domain age days
3061
Apex age days
3061
Tls age days
17
Tls valid days
198
Requests
3
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 49,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Microsoft-IIS/10.0",
    "content-type": "text/html; charset=utf-8",
    "x-powered-by": "ASP.NET"
}

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

Collected source details

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

Every stored field, with its source and date
Website checks · 2026-10-25T06:24:39Z
Mail configuration
{
    "mx": [
        "dfsfiles.com"
    ],
    "spf": "v=spf1 a:host.dfsfiles.com ip4:69.167.176.86 include:_spf.google.com include:_spf.internode.on.net mx ~all",
    "dmarc": true,
    "spf_lookups": 6
}
Caa records
{
    "domain": "dfsfiles.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2025-07-11T08:16:45Z",
    "first": "2011-01-29T07:48:46Z",
    "changes": 7,
    "days_archived": 28,
    "scans_per_day": 0.01,
    "avg_page_bytes": 1366
}
Page title and metadata
{
    "title": "Etab Management System"
}
Trackers
{
    "requests": 2
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 67,
        "tls": 118,
        "wait": 220,
        "connect": 116,
        "download": 1
    },
    "response_ms": 522
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "ocsp_stapled": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        25,
        80,
        110,
        143,
        443,
        587
    ]
}
Carbon
{
    "bytes": 2760,
    "co2_grams": 0.0001,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "173.201.71.24",
            "host": "ns48.domaincontrol.com"
        },
        {
            "ip": "97.74.103.24",
            "host": "ns47.domaincontrol.com"
        }
    ],
    "zone": "dfsfiles.com"
}
Location
{
    "ip": "69.167.176.86",
    "asn": "32244",
    "org": "Liquid Web, L.L.C",
    "city": "Lansing",
    "country": "US"
}
Ssl
{
    "issuer": "GoDaddy.com / GoDaddy TLS Intermediate CA DV - R1v1",
    "subject": "www.dfsfiles.com"
}
DNS records
{
    "A": [
        "69.167.176.86"
    ],
    "MX": [
        "{\"exchange\": \"dfsfiles.com\", \"priority\": 10}"
    ],
    "NS": [
        "ns48.domaincontrol.com",
        "ns47.domaincontrol.com"
    ],
    "SOA": "{\"nsname\": \"ns47.domaincontrol.com\", \"hostmaster\": \"dns.jomax.net\", \"serial\": 2023110103, \"refresh\": 28800, \"retry\": 7200, \"expire\": 604800, \"minttl\": 3600}",
    "TXT": [
        "google-site-verification=iAFrdQgIpeoFZGY2WT_cCfeKP1fs650YK2WGkZ0ROc8",
        "v=spf1 a:host.dfsfiles.com ip4:69.167.176.86 include:_spf.google.com include:_spf.internode.on.net mx ~all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "69.167.176.86",
    "family": 4
}
Redirects
{
    "chain": [
        "https://dfsfiles.com"
    ]
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "www.dfsfiles.com"
    ]
}
Page links
{
    "internal_count": 3
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "created": "2009-07-29T23:11:55Z",
    "updated": "2024-07-30T22:15:32Z",
    "expires": "2027-07-29T23:11:55Z",
    "status": [
        "clientDeleteProhibited https://icann.org/epp",
        "clientRenewProhibited https://icann.org/epp",
        "clientTransferProhibited https://icann.org/epp",
        "clientUpdateProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns47.domaincontrol.com",
        "ns48.domaincontrol.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Microsoft-IIS/10.0",
        "content-type": "text/html; charset=utf-8",
        "x-powered-by": "ASP.NET"
    }
}

Questions about dfsfiles.com

Is dfsfiles.com legit?

No. PhishDestroy classifies dfsfiles.com as a phishing page (risk: critical, 82/100); it was first detected on 2026-10-25. VirusTotal: 6/92 engines flag it. Treat the site as unsafe.

Is dfsfiles.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on dfsfiles.com. 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 dfsfiles.com?

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
Recorded
StateStored capture
HTTP status200
Final URLhttps://dfsfiles.com/
Position1 / 8
Open capture Wayback Download
All capture links and hashes (8)

Domain details

Domain
IP Reputation abuse score 0/100 0 reports checked Oct 25, 2026
Registrar GoDaddy US(US)
Abuse contactabuse@godaddy.com, abuse@liquidweb.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for dfsfiles.com →
RegistrationCreated Jul 29, 2009 — Expires Jul 29, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 78/100
Submitted URLhttp://dfsfiles.com/
Favicon Hash
Case ID
Observed page title
Etab Management System
TLS Certificate
Issued by GoDaddy.com / GoDaddy TLS Intermediate CA DV - R1v1 · stored validity ends in 180 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
69.167.176.86
Network ASN
AS32244
Organization
Liquid Web, L.L.C
Observed location
Lansing, US
Server header
Microsoft-IIS/10.0

Nameservers 2

  • ns47.domaincontrol.com
  • ns48.domaincontrol.com

Mail routing 1 MX record

  • dfsfiles.compriority 10

Location describes the IP network.

TLS certificate

Issuer
GoDaddy.com / GoDaddy TLS Intermediate CA DV - R1v1
Valid from
2026-10-07 22:51:45
Valid until
2027-04-23 22:51:45
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint2efbfbd5528db7d07be18d6c84b369723a43ba969e7acd63c000f4c70f714ead
Certificate names · 5 SANs
  • www.dfsfiles.com
  • dfsfiles.com
  • www.everyrace.com.au
  • www.everyrace.com
  • everyrace.com

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

viewdns.info · 69.167.176.86rapiddns.io
Recorded subdomains1

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

  • www.dfsfiles.comDomain record

The original observation time is not recorded for these hostnames.

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

VirusTotal Analysis

6 / 92 security vendors flagged this domain
View on VT
Last analyzed
BitDefender
CRDF
G-Data
Gridinsoft
SOCRadar
VIPRE

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of dfsfiles.com · checked Oct 25, 2026

100
Good
Performance
FCP
0.76 s
First Contentful Paint
LCP
0.76 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
2.52 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: http://dfsfiles.com/
Etab Management System
Response
HTTP 200
HTML body
2.7 KB
Compressed
1.3 KB
Links
3 internal · 0 external
Selected response headers
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
Server: Microsoft-IIS/10.0
X-Powered-By: ASP.NET
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 9
Cache-Control
private
Content-Encoding
gzip
Content-Length
1607
Content-Type
text/html; charset=utf-8
Date
Sun, 25 Oct 2026 06:24:10 GMT
Server
Microsoft-IIS/10.0
Vary
Accept-Encoding
X-AspNet-Version
2.0.50727
X-Powered-By
ASP.NET

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.

All retained availability observations1

Source: availability monitor. This journal includes earlier observations and repeated states with distinct dates or evidence. Identical records appear once; an unknown state is not proof that the site is offline.

  1. unknown
    Cause
    http_2xx_unclassified
    Monitor confidence
    40
    Original source timestamp
    2026-10-25 07:38:14.000000
    Evidence SHA-256
    73b534d2f22cccbd716035a0d9aae5f3b1e9ee98bb9a332e1451990d0af77cba

Recorded activity

5 entries
  1. Abuse report sent

    PD-20261025-B52B5E

    abuse@godaddy.com
  2. URLScan

    Page captured

    View source
  3. Wayback Machine

    Page archived

    View source
  4. VirusTotal

    6/92 engine detections

    View source
  5. Added to PhishDestroy

    dfsfiles.com

    View source

Check for cloaking

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

dfsfiles.com

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 6 det. ChainPatrol URLQuery 2 det. SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261025-B52B5E Recipient: abuse@godaddy.com
Page title stored with report: Etab Management System
PDF notice generated
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

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 dfsfiles.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)
  • 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

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 →
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/dfsfiles.com"
  title="PhishDestroy threat report for dfsfiles.com"
  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>