Skip to security report
Analytics Dashboard
Domain security and threat intelligence
roaringkitty.fyi favicon

roaringkitty.fyi

In short

roaringkitty.fyi is a fake airdrop scam detected by PhishDestroy on 2026-10-21. Risk: critical (70/100). Registrar: NameCheap. Status: Last known active. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

“Roaring Kitty | Airdrop”

Registrar
NameCheap
Resolved IP
188.114.97.3
Registered
Feb 2, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
Stored blocklist matches: 2 Scam type: Crypto Drainer
Oct 21, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
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@namecheap.com. The latest stored availability evidence still shows the domain reachable; 24 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
24 hours
Reports sent
1
Latest case ID
PD-20261021-394779
Current status
HTTP 200 at latest stored check
VirusTotal
0 / 92
engine detections
Google Safe Browsing
No threat flag
Page captures
4
open gallery
Domain age
262 days
Reports sent
1
view timeline
Source evidenceVirusTotal 0 / 92 5 sources

VirusTotal

0 / 92 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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

Analysis

Critical
VirusTotal
0 / 92
Page captures
4
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy’s intake AI assessed the site as malicious on 2026-10-21, noting that it impersonates the public figure Roaring Kitty and advertises a “Live Roaring Kitty Airdrop” that asks visitors to connect a cryptocurrency wallet to claim tokens. The recorded page title is “Roaring Kitty | Airdrop” and the page returned HTTP 200 on the same date. The domain first appeared in PhishDestroy’s logs on 2026-10-21, 261 days after its registration on 2026-02-02.

How the scam works

In this category of attack, an actor copies a well‑known brand or personality to lure victims into a fake airdrop or giveaway. The victim is prompted to connect a crypto wallet, which can then be used to drain tokens or obtain unauthorized approvals.

Evidence

VirusTotal scanned the domain on 2026-10-10 and reported 0 malicious detections out of 92 engines. Google Safe Browsing checked on 2026-10-21 and did not flag the site. urlscan captured the page on 2026-10-21; its overall verdict was clean, though its machine‑learning engine assigned a malicious score of 89. External blocklists MetaMask and SEAL listed the domain, and PhishDestroy’s internal blocklist also contains it. OTX had no pulses referencing the domain as of the same date.

Infrastructure

The domain was registered with NameCheap on 2026-02-02 and the RDAP record shows a client‑transfer‑prohibited status. Hosting is provided through Cloudflare, with recorded IP addresses 188.114.96.1 and 104.21.91.238. The TLS certificate, issued by Google Trust Services, is valid until 2026-12-25 and covers roaringkitty.fyi and its subdomains. Site technology fingerprints include Node.js, Vue.js, Nuxt.js, lit‑html and Cloudflare’s WAF.

What to do

If a wallet was connected, immediately revoke any token approvals and consider moving assets to a new secure wallet. Defenders should block roaringkitty.fyi at the network perimeter and monitor for any connections to the recorded IPs or Cloudflare endpoints.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-21T15:25:51Z)VirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-10-21T15:31:50Z

Observed: · Retrieved:

Uuid
01a15f16-e8be-71e8-8557-1df2428624f5
Final url
https://roaringkitty.fyi/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://roaringkitty.fyi/",
        "from": "http://roaringkitty.fyi/",
        "status": 307
    }
]
Ip
188.114.97.3
Contacted domains
[
    "fonts.gstatic.com",
    "fonts.googleapis.com",
    "lite-api.jup.ag"
]
Contacted IP addresses
[
    "18.66.122.10",
    "142.251.127.94",
    "2a00:1450:4001:c17::5f",
    "188.114.97.3"
]
Asns
[
    "16509",
    "15169",
    "13335"
]
Countries
[
    "US",
    "DE"
]
Linked domains
[
    "twitter.com",
    "t.me",
    "discord.gg"
]
Social
[
    "https://twitter.com/RoaringKSol",
    "https://t.me/RoaringKittyPortalSolana",
    "https://discord.gg/kitty_token"
]
Document hash
04abfd7d86a13a74f754ae5355202a420240b92361b2d8c47d9205a2cd7a230c
Script hashes
[
    "68aca49eae51242ab668d286b00306bce4f318a7ab9590758b6df253738b1c8a",
    "a14a6f4f294e9a13fc7c78db48a3a3992eca8955e913cc1495f186cd17866694"
]
Globals
[
    "TOKEN_ADDRESS",
    "TOKEN_SYMBOL",
    "INITIAL_PRICE",
    "INITIAL_CHANGE",
    "updateData",
    "_3akj",
    "litPropertyMetadata",
    "reactiveElementVersions",
    "litHtmlVersions",
    "litElementVersions",
    "priceEl",
    "changeEl"
]
Storage keys
[
    "token-price-cache-KITTY",
    "_0x12",
    "_0x5"
]
Tls
{
    "san": [
        "roaringkitty.fyi",
        "*.roaringkitty.fyi"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "roaringkitty.fyi",
    "protocol": "QUIC",
    "valid_to": "2026-12-25T21:10:51Z",
    "valid_from": "2026-09-26T20:12:03Z"
}
Domain age days
774
Apex age days
774
Tls age days
24
Tls valid days
90
Requests
16
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 90,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8"
}
Cloudflare Radar · 2026-10-21T15:25:51Z

Observed: · Retrieved:

Uuid
3f76a502-bb39-4f16-acf8-d5518072abca
Final url
https://roaringkitty.fyi/
Status
200
History
[
    {
        "url": "https://roaringkitty.fyi/",
        "status": 200
    }
]
DOM structure hash
d0e583aacf7a28c22c3c6bb86dc6bf96be611128e2b27925fc6b611e234f0546
Document hash
d40853ba96d25a1cf79dce243d09cf6b5fde8d772d7db71786967420cf149fd7
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "roaringkitty.fyi",
        "type": "A",
        "value": "172.67.181.236"
    },
    {
        "name": "roaringkitty.fyi",
        "type": "A",
        "value": "104.21.91.238"
    }
]
Dnssec valid
false
Ip
172.67.181.236
VirusTotal · 2026-10-10T01:22:01Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 56,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 36
}
Reputation
0
Created
2026-02-02T00:00:00Z
Updated
2026-02-02T00:00:00Z
First seen
2024-09-06T21:56:28Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.91.238"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "dane.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "nena.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "dane.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.181.236"
    }
]
Dns at
2026-10-10T01:24:58Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "roaringkitty.fyi",
        "*.roaringkitty.fyi"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "d278a9317a5498a70e2511372433289d",
    "sha256": "6f88bc6efa5a82a2e95a8aa93dadc406e40ca3aafd951945011af5c4ab9610f5",
    "subject": "roaringkitty.fyi",
    "valid_to": "2026-12-25T21:10:51Z",
    "valid_from": "2026-09-26T20:12:03Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "registration": "2026-02-02T10:43:25Z",
        "registrar expiration": "2027-02-02T10:43:25Z",
        "last update of RDAP database": "2026-10-10T01:24:58Z"
    },
    "registrar": "NAMECHEAP INC",
    "registrar_iana_id": "1068"
}
Website checks · 2026-10-21T15:27:06Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "roaringkitty.fyi"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-05-11T05:17:13Z",
    "first": "2024-09-06T20:21:02Z",
    "changes": 8,
    "days_archived": 14,
    "scans_per_day": 0.02,
    "avg_page_bytes": 10318
}
Page title and metadata
{
    "title": "Roaring Kitty | Airdrop"
}
Trackers
{
    "requests": 14,
    "trackers": [
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 112,
        "tls": 24,
        "wait": 311,
        "connect": 7,
        "download": 1
    },
    "response_ms": 455
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 11446,
    "co2_grams": 0.0004,
    "cleaner_than": 69
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.33.97",
            "host": "dane.ns.cloudflare.com"
        },
        {
            "ip": "162.159.38.161",
            "host": "nena.ns.cloudflare.com"
        }
    ],
    "zone": "roaringkitty.fyi"
}
Location
{
    "ip": "188.114.97.9",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "roaringkitty.fyi"
}
DNS records
{
    "A": [
        "188.114.97.9",
        "188.114.96.9"
    ],
    "NS": [
        "dane.ns.cloudflare.com",
        "nena.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"dane.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2417020593, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
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
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "188.114.97.9",
    "family": 4
}
Redirects
{
    "chain": [
        "https://roaringkitty.fyi"
    ]
}
Tech stack
{
    "technologies": [
        "Node.js",
        "Vue.js",
        "Nuxt.js",
        "lit-html",
        "lit-element",
        "Google Font API",
        "Cloudflare",
        "HTTP/3"
    ]
}
Page links
{
    "external": [
        "https://twitter.com/RoaringKSol",
        "https://t.me/RoaringKittyPortalSolana",
        "https://discord.gg/kitty_token"
    ],
    "external_count": 3,
    "internal_count": 17
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=utf-8"
    }
}

Questions about roaringkitty.fyi

Is roaringkitty.fyi legit?

No. PhishDestroy classifies roaringkitty.fyi as a fake airdrop scam (risk: critical, 70/100); it was first detected on 2026-10-21. Treat the site as unsafe.

Is roaringkitty.fyi safe to connect a wallet?

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

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

Extracted from stored page analysis

Observed indicators

0 wallet · 1 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

Telegram
https://t.me/RoaringKittyPortalSolanaStored page reference

IoC extraction recorded 2026-10-22 04:00:10 UTC

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 4 captures

Primary capture 1 / 4
SourcePrimary capture
Recorded2026-10-21 15:32 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://roaringkitty.fyi/
Position1 / 4
Open capture Wayback Download
Observed page title
Roaring Kitty | Airdrop
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 64 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
Observed indicators0 wallet · 1 Telegram — full values ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar NameCheap US(US)
Abuse contactabuse@namecheap.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for roaringkitty.fyi →
RegistrationCreated Feb 2, 2026 (262d) — Expires Feb 2, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 21, 2026
DOM Analysisanalyzed Oct 21, 2026score 70/100
IoC Extractionscanned Oct 22, 20260 wallet · 1 Telegram IoC
Submitted URLhttp://roaringkitty.fyi/
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • dane.ns.cloudflare.com
  • nena.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-26 20:12:03
Valid until
2026-12-25 21:10:51
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint6f88bc6efa5a82a2e95a8aa93dadc406e40ca3aafd951945011af5c4ab9610f5
Certificate names · 2 SANs
  • roaringkitty.fyi
  • *.roaringkitty.fyi

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

viewdns.info · 188.114.97.3rapiddns.io

Latest Classified Outcome 2026-10-21 23:03:41 UTC

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 Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-21 23:03:41 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-21 23:03:41 UTC last content: 2026-10-21 23:03:41 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.
Recorded subdomains4

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

  • api.roaringkitty.fyiDomain record
  • app.roaringkitty.fyiDomain record
  • sitemaps.roaringkitty.fyiDomain record
  • www.roaringkitty.fyiDomain record

The original observation time is not recorded for these hostnames.

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

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of roaringkitty.fyi · checked Oct 21, 2026

49
Poor
Performance
FCP
3.05s
First Contentful Paint
LCP
7.21s
Largest Contentful Paint
CLS
0.012
Cumulative Layout Shift
TBT
751ms
Total Blocking Time
SI
4.91s
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://roaringkitty.fyi/
Final URL: https://roaringkitty.fyi/
Roaring Kitty | Airdrop
Response
HTTP 200
HTML body
11.5 KB
Compressed
3.9 KB
Links
18 internal · 6 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 14
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a4e145cc6ba59bb2-ARN
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Wed, 21 Oct 2026 15:25:03 GMT
Last-Modified
Mon, 02 Feb 2026 19:21:34 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=f1CdTRlUwdiCxmXzX4OHxa9Q7LCpjt9e3hi9NDBLTMflTuwxjTTc%2BlqGo6yISIOMGHF7xEBCCIk5BDC6%2BJ3wlEcw%2BLytnVztVaNCq6S0QhG3jeTrsVW4lcLTJp1loPKTF7GD"}]}
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
accept-encoding

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

Archived
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.

Stored observation history2

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

    Unknown→live_content

    content_served

  2. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. Abuse report sent

    PD-20261021-394779

    abuse@namecheap.com
  2. URLScan

    Page captured

    View source
  3. Google Safe Browsing

    No threat flag

    View source
  4. VirusTotal

    0/92 engine detections

    View source
  5. Added to PhishDestroy

    roaringkitty.fyi

    View source

Check for cloaking

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

roaringkitty.fyi

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal ChainPatrol URLQuery 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-20261021-394779 Recipient: abuse@namecheap.com
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 Archived
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?

3 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 roaringkitty.fyi)
  • 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/roaringkitty.fyi"
  title="PhishDestroy threat report for roaringkitty.fyi"
  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>