Skip to security report
fees.claimed.work favicon
Domain security and threat intelligence

fees.claimed.work

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

The site fees.claimed.work presents a token market overview interface under the Claimed brand, featuring a prominent button to connect a Web3 wallet via Reown. Visitors should avoid connecting any cryptocurrency wallet or signing authorization requests on this page.

Page title: “Claimed — Token rewards estimate”

More about the sources
Recorded security signals

Listed by external blocklists: ScamSniffer. Use caution — do not enter credentials or personal information.

Spamhaus DBL: phishing domain Stored blocklist matches: 1 Young domain: 11 days old
Registrar
GermanyPDR
Resolved IP
United States188.114.96.3Cloudflare, Inc. · CDN
Registered
2026-11-10
First seen by PhishDestroy
2026-11-20
Page captures
open gallery
Domain age
registered 2026-11-10 according to WHOIS
Reports sent
view timeline
2026-11-20 1 Report Sent CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

ABUSE NOTICE · 24H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@publicdomainregistry.com. The latest stored availability evidence still shows the domain reachable; 32 hours has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
32 hours
Reports sent
1
Latest case ID
PD-08D62C87B5413070B78E
Current status
HTTP 200 at latest stored check

Analysis

Domain summary

PhishDestroy first recorded fees.claimed.work on 2026-11-20. Listed by external blocklists: ScamSniffer. Risk: high (evidence score 58/100). Registrar: PDR. Status: Last known active. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

High
Status
Last known active
Blocklist matches
1 external + PhishDestroy list
Hosting
United States188.114.96.3Cloudflare, Inc. · CDN
Registrar
GermanyPDR
Registered
2026-11-10
Page captures
5

URLScan capture · 2026-11-20 20:29 UTC · SHA-256 27b081a9…5f82940

PhishDestroy analysis, reviewed version

Claimed token market and rewards interface

The page opens on a dark green grid background with the brand name "Claimed" in the top left corner, accompanied by a language toggle for Chinese and a "Connect wallet" button in the upper right. The main headline reads "Your token. One clear view." with a smaller subtitle stating "Explore public token market data and token rewards." Below the header, a search bar invites users to "Paste contract address" alongside an "Explore" button. Further down, the interface displays a card labeled "Token overview" next to a bright green section titled "Token rewards to token holders" which features a dark "Connect wallet" button and small text reading "Estimated rewards are based on the selected token pool and may change with market conditions." Additional metric cards at the bottom show placeholders for token price, market cap, selected pool liquidity, and pool volume, followed by a section titled "The bigger picture" showing a token price chart with time intervals of 15m, 1h, 4h, and 1D.

Wallet connection mechanism and risk

The primary interactive feature on the page is the wallet connection interface powered by Reown, which invites visitors to link their cryptocurrency wallet to view rewards or interact with token pools. Connecting a wallet through this prompt could lead to signing malicious transactions or token approvals that grant unauthorized access to digital assets.

Domain registration and hosting background

It was registered on 10 Nov 2026, 9 days before it was first reported, presenting a brand-new interface while it sits behind Cloudflare, which hides the real server. The domain was registered through PDR Ltd. d/b/a PublicDomainRegistry.com and it still answered requests on 20 Nov 2026 at 21:30 UTC while offering no verified history or established track record under the Claimed brand name.

Source evidence 5 sources

Spamhaus DBL

phishing domain

URLScan

Page capture

SHA-256 58ad4c75…e76b5a0

Open report
URLScanOriginal source recordObserved: 20 fields
Separate monitor record

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a1faa6-04c2-711f-9ad8-382fffe327d3
Enriched at
2026-11-21T09:11:08Z
Source timestamps
Urlscan enriched at: 2026-11-21 10:11:08

PhishDestroy DOM

45 / 100 · heuristic score · 1 brand reference · 0 classifications

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 45 / 100 · 2026-11-20 23:20 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
45
Analyzed at
2026-11-20T23:20:14Z
Source timestamp
2026-11-21 00:20:14
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
fees.claimed.work — Claimed token rewards platform and reown
AI description
fees.claimed.work shows a Claimed token market platform requesting Web3 wallet connections through Reown without an established track record.
AI summary
Claimed token market and rewards interface The page opens on a dark green grid background with the brand name "Claimed" in the top left corner, accompanied by a language toggle for Chinese and a "Connect wallet" button in the upper right. The main headline reads "Your token. One clear view." with a smaller subtitle stating "Explore public token market data and token rewards." Below the header, a search bar invites users to "Paste contract address" alongside an "Explore" button. Further down, the interface displays a card labeled "Token overview" next to a bright green section titled "Token rewards to token holders" which features a dark "Connect wallet" button and small text reading "Estimated rewards are based on the selected token pool and may change with market conditions." Additional metric cards at the bottom show placeholders for token price, market cap, selected pool liquidity, and pool volume, followed by a section titled "The bigger picture" showing a token price chart with time intervals of 15m, 1h, 4h, and 1D. Wallet connection mechanism and risk The primary interactive feature on the page is the wallet connection interface powered by Reown, which invites visitors to link their cryptocurrency wallet to view rewards or interact with token pools. Connecting a wallet through this prompt could lead to signing malicious transactions or token approvals that grant unauthorized access to digital assets. Domain registration and hosting background It was registered on 10 Nov 2026, 9 days before it was first reported, presenting a brand-new interface while it sits behind Cloudflare, which hides the real server. The domain was registered through PDR Ltd. d/b/a PublicDomainRegistry.com and it still answered requests on 20 Nov 2026 at 21:30 UTC while offering no verified history or established track record under the Claimed brand name.
AI generated by
threat-v10-gemini
AI generated at
2026-11-20T21:37:33Z
Revision
aab36883535da6a0ad8a392c260b6ac520e83a6d81ba24c71547ac61e51a8b1e
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

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
VirusTotalOriginal source recordObserved: 12 fields
Open complete records
Website checksOriginal source recordRetrieved: 23 fields

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Page title and metadata

Page title
Claimed — Token rewards estimate
Theme color
#101410

Trackers

Requests
4
Observed services
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
0
Waiting
119
Download
3
Response time, ms
154

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
43791
CO₂, grams
0.0016
Cleaner than, %
40

DNS servers

Nameservers
  • IP address
    162.159.38.128
    Host
    walk.ns.cloudflare.com
  • IP address
    172.64.33.201
    Host
    lynn.ns.cloudflare.com
DNS zone
claimed.work

Page quality

Layout shift (CLS)
0.021
SEO score
92
Speed Index, s
1.66
First Contentful Paint (FCP), s
1.66
Largest Contentful Paint (LCP), s
1.66
Total Blocking Time (TBT), ms
1406
Performance score
74
Accessibility score
100
Best practices score
96

Location

IP address
188.114.96.3
ASN
13335
Organization
Cloudflare, Inc.
City
Francisco
Country
US

TLS certificate

Subject alternative names
  • *.claimed.work
  • claimed.work
Key size, bits
256
Certificate chain
  • claimed.work
  • YE2
  • Root YE
  • ISRG Root X2
  • ISRG Root X1
Issuer
Let's Encrypt / YE2
Serial
05FCF6B9053564398C8E92F659C8F71B0740
SHA-256
1ad2ee07145a85fbbb388708fd2214b6c8bc5015830a1e8d499cddde5c9e8898
Subject
claimed.work
Valid until
Valid from

DNS records

A
  • 188.114.97.3
  • 188.114.96.3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
188.114.96.3
IP version
4

Redirects

Redirect chain
  • https://fees.claimed.work

Technology stack

Technologies
  • Node.js
  • Vue.js
  • Nuxt.js
  • lit-html 3.3.3
  • lit-element 4.2.2
  • Cloudflare
  • HTTP/3

Page links

Internal link addresses
  • https://fees.claimed.work/
  • https://fees.claimed.work/wallet-guide
Internal links
2

Registration record

Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID
303
Registrar URL
publicdomainregistry.com
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
  • serverTransferProhibited https://icann.org/epp
Nameservers
  • lynn.ns.cloudflare.com
  • walk.ns.cloudflare.com
DNSSEC
unsigned

HTTP headers

Response headers
Server
cloudflare
Content-Type
text/html; charset=utf-8
Original source fields · JSON
Protective DNS results
Resolvers: 12; Blocked count: 0
Page title and metadata
Title: Claimed — Token rewards estimate; Themecolor: #101410
Trackers
Requests: 4; Trackers: (Name: Google Fonts; Company: Google; Country: US; Category: Hosting; Requests: 1)
Forms and mixed content
Third party scripts: 0
Status
Up: ✓; Code: 200; Timings: DNS: 0; Wait: 119; Download: 3; Response ms: 154
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
Carbon
Bytes: 43791; Co2 grams: 0.0016; Cleaner than: 40
DNS server
NS: (IP: 162.159.38.128; Host: walk.ns.cloudflare.com), (IP: 172.64.33.201; Host: lynn.ns.cloudflare.com); Zone: claimed.work
Quality
Cls: 0.021; Seo: 92; Si s: 1.66; Fcp s: 1.66; Lcp s: 1.66; Tbt ms: 1406; Performance: 74; Accessibility: 100; Best practices: 96
Location
IP: 188.114.96.3; ASN: 13335; Org: Cloudflare, Inc.; City: Francisco; Country: US
SSL
San: *.claimed.work, claimed.work; Bits: 256; Chain: claimed.work, YE2, Root YE, ISRG Root X2, ISRG Root X1; Issuer: Let's Encrypt / YE2; Serial: 05FCF6B9053564398C8E92F659C8F71B0740; SHA256: 1ad2ee07145a85fbbb388708fd2214b6c8bc5015830a1e8d499cddde5c9e8898; Subject: claimed.work; Valid to: 2027-02-08T20:57:43Z; Valid from: 2026-11-10T20:57:44Z
DNS records
A: 188.114.97.3, 188.114.96.3
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 188.114.96.3; Family: 4
Redirects
Chain: https://fees.claimed.work
Tech stack
Technologies: Node.js, Vue.js, Nuxt.js, lit-html 3.3.3, lit-element 4.2.2, Cloudflare, HTTP/3
Page links
Internal: https://fees.claimed.work/, https://fees.claimed.work/wallet-guide; Internal count: 2
Registration record
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com; Registrar iana ID: 303; Registrar URL: publicdomainregistry.com; Created: 2026-11-10T21:51:41Z; Updated: 2026-11-15T21:51:41Z; Expires: 2027-11-10T21:51:41Z; Status: clientTransferProhibited https://icann.org/epp, serverTransferProhibited https://icann.org/epp; Nameservers: lynn.ns.cloudflare.com, walk.ns.cloudflare.com; Dnssec: unsigned
HTTP headers
Headers: Server: cloudflare; Content type: text/html; charset=utf-8

Questions about fees.claimed.work

Is fees.claimed.work the official Claimed platform?

It was registered on 10 Nov 2026, 9 days before it was first reported. Because the domain has no established history under this brand name, users should exercise caution and verify any token market platform through trusted channels.

What happens if I connect my wallet on fees.claimed.work?

Connecting your wallet through the Reown integration could prompt you to sign transactions or token approvals that grant unauthorized access to your funds. Always disconnect your wallet and revoke any unknown permissions via a trusted block explorer if you already interacted with the page.

Why does the site show market data placeholders?

The interface displays empty fields and generic metric cards to mimic a legitimate token analytics tool. It still answered requests on 20 Nov 2026 at 21:30 UTC, yet the lack of historical trading data reflects its recent creation date.

Explore

Blocklist matches1 external + PhishDestroy list · ScamSniffer · PhishDestroy 1
ScamSniffer Listed View source
PhishDestroy PhishDestroy list View source

Last checked

Page captures (5)

All capture links and hashes (5)
Observed page title
Claimed — Token rewards estimate
Automated brand references
Dexscreener
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 78 days

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 93 report ↗
IP Context United States188.114.96.3 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) PDR DE(DE)
Registration (base domain)claimed.work · Created 2026-11-10 (11d · Very New!) — Expires 2027-11-10
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-20
DOM Analysisanalyzed 2026-11-21score 45/1001 brand signal
Submitted URLhttps://fees.claimed.work/
Case ID
ICANN OVERSIGHT Registration: claimed.work

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

Registrable domain behind this subdomain: claimed.work. For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States188.114.96.3
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
United StatesFrancisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • lynn.ns.cloudflare.com
  • walk.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-11-10 20:57:44
Valid until
2027-02-08 20:57:43
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint1ad2ee07145a85fbbb388708fd2214b6c8bc5015830a1e8d499cddde5c9e8898
Certificate names · 2 SANs
  • *.claimed.work
  • claimed.work

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

Latest Classified Outcome 2026-11-21 23:55 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-21 12:02 UTC
RDAP registration
Observed timeline last reachable: 2026-11-21 23:55 UTC last content: 2026-11-21 23:55 UTC
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.
Technologies · 6 identified
Open complete records
PageSpeed (mobile): 75

Google PageSpeed Insights — mobile performance audit of fees.claimed.work ·

75
Needs Work
Performance
FCP
1.66 s
First Contentful Paint
LCP
1.66 s
Largest Contentful Paint
CLS
0.021
Cumulative Layout Shift
TBT
1236 ms
Total Blocking Time
SI
1.66 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 522
Requested URL: https://fees.claimed.work/
claimed.work | 522: Connection timed out
Response
HTTP 522
HTML body
7.1 KB
Compressed
2.1 KB
Links
4 internal · 1 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Server: cloudflare
Security headers present
X-Frame-OptionsReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 13
Alt-Svc
h3=":443"; ma=86400
Cache-Control
private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
CF-RAY
a5da390ad9462103-LHR
Connection
keep-alive
Content-Length
7249
Content-Type
text/html; charset=UTF-8
Date
Fri, 20 Nov 2026 20:32:33 GMT
Expires
Thu, 01 Jan 1970 00:00:01 GMT
Referrer-Policy
same-origin
Retry-After
120
Server
cloudflare
Server-Timing
cfEdge;dur=19275,cfOrigin;dur=0
X-Frame-Options
SAMEORIGIN

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

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

All stored data113
Open complete records

Captured network requests

Network requests: 34 SHA-256 hashes: 28 URLScan scan:

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-11-21 03:30 UTC.

Open this scan on URLScan 01a1fc26-827b-773c-af94-1f0386eabac0 ↗

Stored observation history3

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

  1. Availability monitor · Recorded state

    Serving page content

    page content returned

  2. Availability monitor · Recorded state

    Serving page content

    page content returned

  3. Domain monitor · First collection record

    Reachable

All retained availability observations5
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · in progress

Recorded events: 10. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    fees.claimed.work detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Blocklist Detection · Forensic Evidence Collected · Technical Analysis Recorded recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: PDR Ltd. d/b/a PublicDomainRegistry.com. Abuse contacts: 1.
    • abuse@publicdomainregistry.com
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

3 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+9 d 22 h
  3. First abuse report sent+7 h 2 min

Reported 10 d 5 h after registration

  1. Abuse report sent

    PD-08D62C87B5413070B78E · Receipt 85468

    abuse@publicdomainregistry.com
    +2 min
  2. URLScan

    Page captured

    +7 h 0 min
  3. Added to PhishDestroy

    fees.claimed.work

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

fees.claimed.work

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-08D62C87B5413070B78E Recipient: abuse@publicdomainregistry.com
PDF notice generated Notice text archived (395 characters)
Abuse notice text as sent to the provider
Registrar policy. Per PDR Ltd. d/b/a PublicDomainRegistry.com's published terms: “Explicit policy to immediately suspend domains used for phishing, 419 scams, identity fraud, malware distribution without prior notice”
Applicable law. Domestic legal framework (India): IT Act 2000 §§66C–66D (identity theft, cheating by personation), Indian Penal Code §420 / Bharatiya Nyaya Sanhita §318 (fraud).
Deep Analysis

Were You Affected by This Site?

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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

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.

  • 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 fees.claimed.work)
  • 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

Stay Informed, Stay Safe

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

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.

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/fees.claimed.work"
  title="PhishDestroy threat report for fees.claimed.work"
  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>