Skip to security report
snapfy.site favicon
Domain security and threat intelligence

snapfy.site

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

On 2026-11-09, snapfy.site displayed a dark-themed page branded "SNAPFY.SITE" in the header, with cartoon avatar figures above a text field labeled "Enter Username" and a yellow "CONNECT" button. Below this, a scrolling ticker showed repeated notices such as "Someone accessed @emma_luv's Best Friends" and similar entries for other usernames. The page then lists selectable options with icons and short descriptions: "Best Friend List" (Reveal 8 Best friends of any user), "Snapping With Mod" (Find out who they're snapping with), "My Eyes Only" (Request My Eyes Only memories), "Snap Score" (See who checked your snapscore), "Chat History" (Request Chat History, Talk History), and "Snap Recap 2025" (View 2025 Recap of any user).

Page title: “Snapfy - Snapchat Tools”

More about the sources
Recorded security signals

Stored VirusTotal result: 2/92 engines flagged. Malicious: 1. Suspicious: 1. Analysis time (as stored): 2026-11-06 06:54 UTC. Retrieved (as stored): 2026-11-09 21:44 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 2/92
Registrar
LithuaniaHostinger
Resolved IP
Canada104.21.40.183Cloudflare, Inc. · CDN
Registered
2026-03-22
First seen by PhishDestroy
2026-11-09
URLQuery
detections
Page captures
open gallery
Domain age
registered 2026-03-22 according to WHOIS · source data differ
Reports sent
view timeline
2026-11-09 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.

Analysis

Domain summary

PhishDestroy first recorded snapfy.site on 2026-11-09. Stored VirusTotal result: 2/92 engines flagged. Malicious: 1. Suspicious: 1. Analysis time (as stored): 2026-11-06 06:54 UTC. Retrieved (as stored): 2026-11-09 21:44 UTC. Risk: critical (evidence score 80/100). Registrar: Hostinger. Status: Content unavailable. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Content unavailable
VirusTotal
2 / 92
Hosting
Canada104.21.40.183Cloudflare, Inc. · CDN
Registrar
LithuaniaHostinger
Registered
2026-03-22
Page captures
5

URLScan capture · 2026-11-09 21:42 UTC · SHA-256 630ff59b…3ce7715

PhishDestroy analysis, reviewed version

On 2026-11-09, snapfy.site displayed a dark-themed page branded "SNAPFY.SITE" in the header, with cartoon avatar figures above a text field labeled "Enter Username" and a yellow "CONNECT" button. Below this, a scrolling ticker showed repeated notices such as "Someone accessed @emma_luv's Best Friends" and similar entries for other usernames. The page then lists selectable options with icons and short descriptions: "Best Friend List" (Reveal 8 Best friends of any user), "Snapping With Mod" (Find out who they're snapping with), "My Eyes Only" (Request My Eyes Only memories), "Snap Score" (See who checked your snapscore), "Chat History" (Request Chat History, Talk History), and "Snap Recap 2025" (View 2025 Recap of any user).

The stored VirusTotal domain result reports 2 detections out of 92 engines. Webroot reported "malicious"; Gridinsoft reported "suspicious".

Source evidenceVirusTotal 2 / 92 7 sources

VirusTotal

2 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 12 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
4
Denominator
92
Vendors
alphaMountain.ai, Forcepoint ThreatSeeker, SOCRadar, Webroot
Checked at
2026-11-13 04:04:25
Fetched at
2026-11-13 03:04:25

URLScan

Malicious

SHA-256 f3bed76b…4a7c812

Open report
URLScanOriginal source recordObserved: 19 fields
Separate monitor record · 2026-11-10 04:30 UTC

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

UUID
01a1c242-e0ce-746a-baa3-86d41454949f
Score
100
Malicious
✓
Result at
2026-11-10T04:30:12Z
Enriched at
2026-11-10T09:11:39Z
Source timestamps
Urlscan result at: 2026-11-10 05:30:12; Urlscan enriched at: 2026-11-10 10:11:39

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields
Separate stored summary: clean

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

Verdict
clean
Source path
phishdestroy.technologies.cf_radar
Scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

PhishDestroy DOM

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

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 15 / 100 · 2026-11-09 22:16 UTC

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

Heuristic score
15
Analyzed at
2026-11-09T22:16:54Z
Source timestamp
2026-11-09 23:16:54
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
snapfy.site: Recorded username-connect tool page with feature list
AI description
PhishDestroy records snapfy.site as a page offering a username entry field, a connect button and a list of account-related feature options.
AI summary
On 2026-11-09, snapfy.site displayed a dark-themed page branded "SNAPFY.SITE" in the header, with cartoon avatar figures above a text field labeled "Enter Username" and a yellow "CONNECT" button. Below this, a scrolling ticker showed repeated notices such as "Someone accessed @emma_luv's Best Friends" and similar entries for other usernames. The page then lists selectable options with icons and short descriptions: "Best Friend List" (Reveal 8 Best friends of any user), "Snapping With Mod" (Find out who they're snapping with), "My Eyes Only" (Request My Eyes Only memories), "Snap Score" (See who checked your snapscore), "Chat History" (Request Chat History, Talk History), and "Snap Recap 2025" (View 2025 Recap of any user). The stored VirusTotal domain result reports 2 detections out of 92 engines. Webroot reported "malicious"; Gridinsoft reported "suspicious".
AI generated by
threat-v6-mimo
AI generated at
2026-11-09T21:47:26Z
Revision
9e7076b8920dc17c66ae0dc36c7937c5eb867e805d3ca59dd91c778e339dd4c3
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: 24 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
3
Archived days
5
Snapshots per day
0
Average page size, bytes
81625

Crawler rules

User agents
  • *
  • Amazonbot
  • Applebot-Extended
  • Bytespider
  • CCBot
Present
Yes

Page title and metadata

Page title
Snapfy - Snapchat Tools

Trackers

Requests
7
Observed services
  • Name
    Amazon CloudFront
    Company
    Amazon
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://cdn.tailwindcss.com/
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
10
TLS
17
Waiting
78
Connection
8
Download
26
Response time, ms
139

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
556561
CO₂, grams
0.0204
Cleaner than, %
1

DNS servers

Nameservers
  • IP address
    172.64.33.238
    Host
    thomas.ns.cloudflare.com
  • IP address
    108.162.194.232
    Host
    angelina.ns.cloudflare.com
DNS zone
snapfy.site

Location

IP address
2606:4700:3030::ac43:9c48
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Google Trust Services / WE1
Subject
snapfy.site

DNS records

A
  • 172.67.156.72
  • 104.21.40.183
NS
  • thomas.ns.cloudflare.com
  • angelina.ns.cloudflare.com
SOA
Primary nameserver
angelina.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2419326838
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:3030::6815:28b7
  • 2606:4700:3030::ac43:9c48

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
strict-origin-when-cross-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
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
2606:4700:3030::6815:28b7
IP version
6

Redirects

Redirect chain
  • https://snapfy.site

Technology stack

Technologies
  • Tailwind CSS
  • Font Awesome
  • cdnjs
  • Cloudflare
  • HTTP/3

Registration record

Registrar
HOSTINGER operations, UAB
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • angelina.ns.cloudflare.com
  • thomas.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-Type
text/html; charset=utf-8
X-Content-Type-Options
nosniff
Referrer-Policy
strict-origin-when-cross-origin
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
Web archive observations
Last: 2026-11-09T21:45:12Z; First: 2024-05-28T00:59:33Z; Changes: 3; Days archived: 5; Scans per day: 0; Avg page bytes: 81625
Crawler rules
Agents: *, Amazonbot, Applebot-Extended, Bytespider, CCBot; Present: ✓
Page title and metadata
Title: Snapfy - Snapchat Tools
Trackers
Requests: 7; Trackers: (Name: Amazon CloudFront; Company: Amazon; Country: US; Category: Hosting; Requests: 1), (Name: Cloudflare; Company: Cloudflare; Country: US; Category: Hosting; Requests: 1)
Forms and mixed content
No sri: https://cdn.tailwindcss.com/; Third party scripts: 1
Status
Up: ✓; Code: 200; Timings: DNS: 10; TLS: 17; Wait: 78; Connect: 8; Download: 26; Response ms: 139
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
Carbon
Bytes: 556561; Co2 grams: 0.0204; Cleaner than: 1
DNS server
NS: (IP: 172.64.33.238; Host: thomas.ns.cloudflare.com), (IP: 108.162.194.232; Host: angelina.ns.cloudflare.com); Zone: snapfy.site
Location
IP: 2606:4700:3030::ac43:9c48; ASN: 13335; Org: Cloudflare, Inc.; City: Toronto; Country: CA
SSL
Issuer: Google Trust Services / WE1; Subject: snapfy.site
DNS records
A: 172.67.156.72, 104.21.40.183; NS: thomas.ns.cloudflare.com, angelina.ns.cloudflare.com; Soa: Nsname: angelina.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2419326838; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2606:4700:3030::6815:28b7, 2606:4700:3030::ac43:9c48
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: strict-origin-when-cross-origin; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2606:4700:3030::6815:28b7; Family: 6
Redirects
Chain: https://snapfy.site
Tech stack
Technologies: Tailwind CSS, Font Awesome, cdnjs, Cloudflare, HTTP/3
Registration record
Registrar: HOSTINGER operations, UAB; Created: 2026-03-22T15:52:47Z; Updated: 2026-07-09T14:06:45Z; Expires: 2027-03-22T15:52:47Z; Status: clientTransferProhibited https://icann.org/epp; Nameservers: angelina.ns.cloudflare.com, thomas.ns.cloudflare.com
HTTP headers
Headers: Server: cloudflare; Content type: text/html; charset=utf-8; X content type options: nosniff; Referrer policy: strict-origin-when-cross-origin
Security Signals
SA Scamadviser Warnings 50/100
The Tranco rank (how much traffic) is rather low The age of this site is (very) young.
We found a valid SSL certificate DNSFilter labels this site as safe

Questions about snapfy.site

Is snapfy.site legit?

PhishDestroy rates snapfy.site as critical risk (evidence score 80/100) from the recorded evidence; it was first recorded on 2026-11-09. Stored VirusTotal result: 2/92 engines flagged. Malicious: 1. Suspicious: 1. Analysis time (as stored): 2026-11-06 06:54 UTC. Retrieved (as stored): 2026-11-09 21:44 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is snapfy.site safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on snapfy.site. A confirmed blockchain transaction cannot be reversed.

What should I do if I used snapfy.site?

  • 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
  • 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
  • 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
  • Downloaded a file — do not open it and scan the device with security software

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. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (5)

All capture links and hashes (5)
Observed page title
Snapfy - Snapchat Tools
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 57 days

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Snapchat report ↗
IP Context Canada104.21.40.183 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Hostinger LT(LT)
Abuse contactabuse@hostinger.com
RegistrationCreated 2026-03-22 (245d) — Expires 2027-03-22
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-09
DOM Analysisanalyzed 2026-11-09score 15/100
Submitted URLhttps://snapfy.site/
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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada104.21.40.183
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • angelina.ns.cloudflare.com
  • thomas.ns.cloudflare.com

SOA

  • nsname: angelina.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2419326838
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-10-21 16:16:20
Valid until
2027-01-19 17:16:17
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint5fa00258f8e270be06cbdd33accc85e4e1d38c86519cd8af6f185bef39696a51
Certificate names · 1 SAN
  • snapfy.site

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-22 06:03 UTC

The domain no longer resolves in DNS.

Technical details
Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN
RDAP registration
Observed timeline last reachable: 2026-11-09 21:43 UTC current episode first observed: 2026-11-09 22:22 UTC observed RIP window: 2026-11-09 21:43 UTC → 2026-11-09 22:22 UTC · 0.65h midpoint estimate ≈ 2026-11-09 22:02 UTC · precision high · basis bounded
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 subdomains1

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

  • www.snapfy.siteDomain record
Technologies · 4 identified
Open complete records

VirusTotal Analysis

2 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 2 detections
Webroot
Gridinsoft

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

PageSpeed (mobile): 63

Google PageSpeed Insights — mobile performance audit of snapfy.site ·

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

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

Archived HTTP response HTTP 200
Requested URL: https://snapfy.site/
Snapfy - Snapchat Tools
Response
HTTP 200
HTML body
543.9 KB
Compressed
394.7 KB
Links
0 internal · 0 external
Detected technologies
vuecloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Cache-Control: public, max-age=0, must-revalidate
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Security headers present
X-Content-Type-OptionsReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 17
Access-Control-Allow-Origin
*
Alt-Svc
h3=":443"; ma=86400
Cache-Control
public, max-age=0, must-revalidate
cf-cache-status
DYNAMIC
CF-RAY
a57fff5658f117dd-AMS
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Mon, 09 Nov 2026 21:44:12 GMT
NEL
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Referrer-Policy
strict-origin-when-cross-origin
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=%2FB8bTcgk5QTFQiib1%2BYbbz8LUZg1%2FV3x7aALtj3clTxml1%2Bp%2BX9nbuMTBdW36LFX4oAaXgJuZ1gkncJnSc62x4uTYvN56F2mDSFGBAXUSK16427oEikBYufkZHo9%2FQ%3D%3
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
accept-encoding
X-Content-Type-Options
nosniff

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

Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
0.65
Estimate basis
Bounded by observations
Estimate precision
High

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

All stored data125
Open complete records

Captured network requests

Network requests: 14 SHA-256 hashes: 10 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-09 21:45 UTC.

Open this scan on URLScan 01a1c242-e0ce-746a-baa3-86d41454949f ↗

Stored observation history8

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

    Not resolving in DNS

    domain does not exist in DNS

  2. Availability monitor · Recorded state

    Not resolving in DNS

    domain does not exist in DNS

  3. Domain monitor · Recorded state

    Reachable→Unavailable

  4. Availability monitor · Recorded state

    Not resolving in DNS

    domain does not exist in DNS

  5. Availability monitor · Recorded state

    Not resolving in DNS

    domain does not exist in DNS

Earlier observations 3
  1. Availability monitor · Recorded state

    Not resolving in DNS

    domain does not exist in DNS

  2. Availability monitor · Recorded state

    Not resolving in DNS

    domain does not exist in DNS

  3. Domain monitor · First collection record

    Reachable

All retained availability observations25
Open complete records

Threat Response Pipeline

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

Recorded events: 13. 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
    snapfy.site detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Automated brand label: Snapchat · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: HOSTINGER operations, UAB. Abuse contacts: 1.
    • abuse@hostinger.com
Publication & AvailabilityDestroyList Published · Content Observed Unavailable recorded
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Content Observed Unavailable
    The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.

Recorded activity

7 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+228 d 15 h
  3. Added to PhishDestroy+3 d 14 h
  4. First abuse report sent+1 min

Reported 232 d 5 h after registration

  1. Hostinger

    Took action

    +18 min
  2. Cloudflare Radar

    Phishing

    same minute
  3. Wayback Machine

    Page archived

    same minute
  4. Abuse report sent

    PD-1F929D3DAAEBC533DBEE · Receipt 84596

    abuse@hostinger.com
    +1 min
  5. Added to PhishDestroy

    snapfy.site

    same minute
  6. URLScan

    Page captured

    +3 d 14 h
  7. VirusTotal

    2/92 engine detections

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.

snapfy.site

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-1F929D3DAAEBC533DBEE Recipient: abuse@hostinger.com
Page title stored with report: Snapfy - Snapchat Tools
PDF notice generated
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 snapfy.site)
  • 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/snapfy.site"
  title="PhishDestroy threat report for snapfy.site"
  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>