Skip to security report
Analytics Dashboard
Suspicious Domain — Listed on PhishDestroy
Stored PhishDestroy threat listing. VirusTotal analysis stored; no vendor detections were recorded at check time. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
fs.refa3y.cc favicon

fs.refa3y.cc

In short

PhishDestroy records that fs.refa3y.cc returned a connection reset error page instead of loading any site content.

“fs.refa3y.cc”

Review the evidence
Registrar
United StatesGlobal Domain Group
Resolved IP
United States23.94.153.146HostPapa
Registered
Oct 25, 2026
First observed
Oct 30, 2026
PhishDestroy assessment Medium
25/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
Stored PhishDestroy threat listing Young domain: 5 days old
VirusTotal
0 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 100
Page captures
3
open gallery
Domain age
5 days
registered 2026-10-25 according to WHOIS
Oct 30, 2026
X Telegram API

Analysis

Medium
Status
Last known active
VirusTotal
0 / 92
Hosting
United States23.94.153.146HostPapa
Registrar
United StatesGlobal Domain Group
Registered
Oct 25, 2026
Page captures
3
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page for fs.refa3y.cc is a browser error screen rather than a website. It shows the heading "This site can't be reached" with the message "The connection was reset" and the error code ERR_CONNECTION_RESET, along with suggestions to check the connection, proxy, or firewall. The only interactions offered are Details and Reload buttons, so no site content, branding, or form was reachable at capture time. This conflicts with earlier metadata describing a login page, which the screenshot does not support.

The stored VirusTotal domain result reports 0 detections out of 92 engines.

Source evidenceVirusTotal 0 / 92 8 sources

URLScan

Malicious · engine verdict · score 100

SHA-256 04d05978fdb111358073ab0524e5c1fafc0826615c206987618416b8bd8a4747

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a18c3e-9758-7532-a6e6-eb7c8589a552

Final URL

https://fs.refa3y.cc/indexx.php

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://fs.refa3y.cc/indexx.php
    From
    http://fs.refa3y.cc/indexx.php
    Status
    307

IP address

23.94.153.146

Reverse DNS (PTR)

23-94-153-146-host.colocrossing.com

Contacted domains

  • developer.apple.com
  • upload.wikimedia.org
  • onlinebanking.faisalbank.com.eg

Contacted IP addresses

  • 2a01:b740:a10:f100::200
  • 2a02:ec80:300:ed1a::2:b
  • 23.94.153.146

Autonomous systems (ASN)

  • 6185
  • 14907
  • 36352

Server countries

  • DE
  • US

Document hash

04d05978fdb111358073ab0524e5c1fafc0826615c206987618416b8bd8a4747

JavaScript globals

  • togglePassword
  • pins

Domain age, days

0

Registered domain age, days

2

Certificate age, days

6197

Certificate validity, days

3650

Page requests

7

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
100
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Content-type
image/png
Original source fields · JSON
Uuid
01a18c3e-9758-7532-a6e6-eb7c8589a552
Final url
https://fs.refa3y.cc/indexx.php
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://fs.refa3y.cc/indexx.php",
        "from": "http://fs.refa3y.cc/indexx.php",
        "status": 307
    }
]
Ip
23.94.153.146
Ptr
23-94-153-146-host.colocrossing.com
Contacted domains
[
    "developer.apple.com",
    "upload.wikimedia.org",
    "onlinebanking.faisalbank.com.eg"
]
Contacted IP addresses
[
    "2a01:b740:a10:f100::200",
    "2a02:ec80:300:ed1a::2:b",
    "23.94.153.146"
]
Asns
[
    "6185",
    "14907",
    "36352"
]
Countries
[
    "DE",
    "US"
]
Document hash
04d05978fdb111358073ab0524e5c1fafc0826615c206987618416b8bd8a4747
Globals
[
    "togglePassword",
    "pins"
]
Domain age days
0
Apex age days
2
Tls age days
6197
Tls valid days
3650
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "image/png"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a18c3e-9758-7532-a6e6-eb7c8589a552
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

VirusTotal

0 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
0
Malicious
0
Suspicious
0
Undetected
92

Reputation score

0

Tags

  • self-signed
  • dga

Created

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    23.94.153.146

DNS records observed

JARM fingerprint

2ad2ad16d2ad2ad00042d42d00000061256d32ed7779c14686ad100544dc8d

Certificate

Issuer
localhost
Serial
b5c752c98781b503
SHA-256
016973380c0f1df00bd9593ed8d5efa3706cd6df7993f6141272b80522acdd23
Subject
localhost
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 0,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 92
}
Reputation
0
Tags
[
    "self-signed",
    "dga"
]
Created
2026-10-25T00:00:00Z
First seen
2026-10-30T09:57:21Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "23.94.153.146"
    }
]
Dns at
2026-10-30T09:57:21Z
Jarm
2ad2ad16d2ad2ad00042d42d00000061256d32ed7779c14686ad100544dc8d
Certificate
{
    "issuer": "localhost",
    "serial": "b5c752c98781b503",
    "sha256": "016973380c0f1df00bd9593ed8d5efa3706cd6df7993f6141272b80522acdd23",
    "subject": "localhost",
    "valid_to": "2019-11-08T23:48:47Z",
    "valid_from": "2009-11-10T23:48:47Z"
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-10-30 09:57:18 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-30T09:57:18Z
fetched_at
2026-10-30T09:59:05Z
stats
{"timeout":0,"harmless":0,"malicious":0,"suspicious":0,"undetected":92}

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Report ID

1d28cbd3-83b0-4ef6-87f0-d05c04536f33

Final URL

https://fs.refa3y.cc/

Navigation history

  • URL
    https://fs.refa3y.cc/
    Status
    0

DOM structure hash

98bd88916dd950b8235aa4ffd9739350aff34af92069b19d70ec650951d9da5d

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    fs.refa3y.cc
    Type
    A
    Value
    23.94.153.146

DNSSEC valid

No

Registration record

Registrar
Global Domain Group LLC
Registered
Updated
Expires
Nameservers
  • nancy.ns.cloudflare.com
  • noel.ns.cloudflare.com
Original source fields · JSON
Uuid
1d28cbd3-83b0-4ef6-87f0-d05c04536f33
Final url
https://fs.refa3y.cc/
History
[
    {
        "url": "https://fs.refa3y.cc/",
        "status": 0
    }
]
DOM structure hash
98bd88916dd950b8235aa4ffd9739350aff34af92069b19d70ec650951d9da5d
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "fs.refa3y.cc",
        "type": "A",
        "value": "23.94.153.146"
    }
]
Dnssec valid
false
Registration record
{
    "registrar": "Global Domain Group LLC",
    "created": "2026-10-25T09:47:31Z",
    "updated": "2026-10-25T09:48:57Z",
    "expires": "2027-10-25T09:47:31Z",
    "nameservers": [
        "nancy.ns.cloudflare.com",
        "noel.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

0 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-30T10:18:35Z

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

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-10-30T10:18:35Z
source_timestamp
2026-10-30 11:18:35
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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
fs.refa3y.cc — connection reset error page
ai_description
PhishDestroy records that fs.refa3y.cc returned a connection reset error page instead of loading any site content.
ai_summary
The captured page for fs.refa3y.cc is a browser error screen rather than a website. It shows the heading "This site can't be reached" with the message "The connection was reset" and the error code ERR_CONNECTION_RESET, along with suggestions to check the connection, proxy, or firewall. The only interactions offered are Details and Reload buttons, so no site content, branding, or form was reachable at capture time. This conflicts with earlier metadata describing a login page, which the screenshot does not support. The stored VirusTotal domain result reports 0 detections out of 92 engines.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-30 11:00:36
revision
332bb05b0fa4881aeef5d13351c164c5a537c6d26cee68c0b1371d606ac96348
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
Website checksOriginal source recordRetrieved: 12 fields

CAA records

Domain
fs.refa3y.cc

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Trackers

Requests
2

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
No
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 3306
  • 3389

DNS servers

Nameservers
  • IP address
    108.162.194.84
    Host
    nancy.ns.cloudflare.com
  • IP address
    172.64.33.216
    Host
    noel.ns.cloudflare.com
DNS zone
refa3y.cc

Location

IP address
23.94.153.146
ASN
36352
Organization
HostPapa
City
Buffalo
Country
US

TLS certificate

Issuer
localhost
Subject
localhost

DNS records

A
  • 23.94.153.146

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
23.94.153.146
IP version
4

Registration record

Registrar
Global Domain Group LLC
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • nancy.ns.cloudflare.com
  • noel.ns.cloudflare.com
Original source fields · JSON
Caa records
{
    "domain": "fs.refa3y.cc"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Trackers
{
    "requests": 2
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": false,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        3306,
        3389
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.194.84",
            "host": "nancy.ns.cloudflare.com"
        },
        {
            "ip": "172.64.33.216",
            "host": "noel.ns.cloudflare.com"
        }
    ],
    "zone": "refa3y.cc"
}
Location
{
    "ip": "23.94.153.146",
    "asn": "36352",
    "org": "HostPapa",
    "city": "Buffalo",
    "country": "US"
}
Ssl
{
    "issuer": "localhost",
    "subject": "localhost"
}
DNS records
{
    "A": [
        "23.94.153.146"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "23.94.153.146",
    "family": 4
}
Registration record
{
    "registrar": "Global Domain Group LLC",
    "created": "2026-10-25T09:47:31Z",
    "updated": "2026-10-25T09:48:57Z",
    "expires": "2027-10-25T09:47:31Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "nancy.ns.cloudflare.com",
        "noel.ns.cloudflare.com"
    ]
}

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 3 captures

Cloudflare Radar 1 / 3 Used in the analysis Source file SHA-256: a5db7ab655d3900bfb2bf44f8483ca7ce06fc6f795376f14b777be50f1f0af62 SHA-256 of the prepared copy given to the model: 9b2bd0fda53e1c8aebf8b218f9819433925b9342fe39730c23b507fc9285f8eb
SourceCloudflare Radar
Recorded
StateStored capture
Final URLhttps://fs.refa3y.cc/
Position1 / 3
Open capture Source Report Wayback Download
All capture links and hashes (3)
fs.refa3y.cc: under review, risk score 25/100 (medium); not yet listed by external security vendors.
Social preview card fs.refa3y.cc: under review, risk score 25/100 (medium); not yet listed by external security vendors. v a88537fc6217

Domain details

Domain
IP Reputation United States23.94.153.146 abuse score 0/100 0 reports checked Oct 30, 2026
Registrar (base domain) Global Domain Group US(US)
Abuse contactnet-abuse-global@hostpapa.com, abuse@globaldomaingroup.com, abuse@colocrossing.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for refa3y.cc →
Hosting abuse contact net-abuse-global@hostpapa.com HostPapa · AS36352
Registration (base domain)refa3y.cc · Created Oct 25, 2026 (5d · Brand New!) — Expires Oct 25, 2027
WHOIS statusclientTransferProhibited
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 30, 2026
DOM Analysisanalyzed Oct 30, 2026score 0/100
Submitted URLhttp://fs.refa3y.cc/indexx.php
Favicon Hash
Observed page title
fs.refa3y.cc
TLS Certificate
Issued by localhost

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States23.94.153.146
Network ASN
AS36352
Organization
HostPapa
Observed location
United StatesBuffalo, US
Server header
Apache/2.4.58 (Win64) OpenSSL/3.1.3 PHP/8.2.12

Nameservers 2

  • nancy.ns.cloudflare.com
  • noel.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
localhost
Valid from
2009-11-10 23:48:47
Valid until
2019-11-08 23:48:47
Validity
Stored certificate expired
Collection time
2026-10-30 11:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint016973380c0f1df00bd9593ed8d5efa3706cd6df7993f6141272b80522acdd23

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.94.153.146rapiddns.io
Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
View Archive
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://fs.refa3y.cc/indexx.php
Faisal Islamic Bank – Login
Response
HTTP 200
HTML body
11.3 KB
Compressed
3.3 KB
Links
4 internal · 0 external
Detected technologies
apache
Selected response headers
Server: Apache/2.4.58 (Win64) OpenSSL/3.1.3 PHP/8.2.12
X-Powered-By: PHP/8.2.12
Content-Type: text/html; charset=UTF-8
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 1d7c95c5eea00a8083a95810f902682f9e26e7fbb7876b022a403642d776d0c9
Saved response-header values · 7
Connection
Keep-Alive
Content-Type
text/html; charset=UTF-8
Date
Fri, 30 Oct 2026 09:59:24 GMT
Keep-Alive
timeout=5, max=100
Server
Apache/2.4.58 (Win64) OpenSSL/3.1.3 PHP/8.2.12
Transfer-Encoding
chunked
X-Powered-By
PHP/8.2.12

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.

Captured network requests

Network requests: 7 SHA-256 hashes: 6 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-10-30 09:59 UTC.

Open this scan on URLScan 01a18c3e-9758-7532-a6e6-eb7c8589a552 ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
fs.refa3y.cc
Crawler
NBE Rewards - Login
fs.refa3y.cc
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. Domain monitor · First collection record

    Reachable

All retained availability observations2

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 10:58:47.000000
    Evidence SHA-256
    49dd774a333dbbb68c67e5502b31686b2e0101e375dbf1cae711c967aaaccabb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 10:58:47
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 10:58:47.000000
    Evidence SHA-256
    49dd774a333dbbb68c67e5502b31686b2e0101e375dbf1cae711c967aaaccabb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 10:58:47
    Evidence reason

Threat Response Pipeline

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

Recorded events: 8. 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: 1 of 1
  • Threat Ingested
    fs.refa3y.cc detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 100
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. Wayback Machine

    Page archived

    View source
  2. Added to PhishDestroy

    fs.refa3y.cc

    View source
  3. URLScan

    Page captured

    View source
  4. VirusTotal

    0/92 engine detections

    View source
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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal ChainPatrol URLQuery SSL Labs CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
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?

2 evidence signal groups linked Last known active
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. Silence is the scammer’s greatest advantage. Break it.
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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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.

  • 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

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 fs.refa3y.cc)
  • 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

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/fs.refa3y.cc"
  title="PhishDestroy threat report for fs.refa3y.cc"
  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>