Skip to security report
Caution

Flagged by threat-detection services

gethelpp.top favicon
Domain security and threat intelligence

gethelpp.top

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

gethelpp.top: VirusTotal 0/92 detections. First recorded 2026-11-21. Registrar: PDR Ltd.

More about the sources

Use caution — do not enter credentials or personal information.

Stored PhishDestroy threat listing Young domain: 6 days old Last known active
Registrar
United StatesPDR
Resolved IP
Canada104.21.27.174Cloudflare, Inc. · CDN
Registered
2026-11-16
First seen by PhishDestroy
2026-11-21
Page captures
open gallery
Reports sent
view timeline
2026-11-21 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

Medium
Status
Reachable · access restricted
Hosting
Canada104.21.27.174Cloudflare, Inc. · CDN
Registrar
United StatesPDR
Registered
2026-11-16
Page captures
5

Recorded source summary

PhishDestroy first observed gethelpp.top on Nov 21, 2026. Current evidence score: 25/100 (medium).

VirusTotal recorded 0 detections among 92 engines on Nov 21, 2026 at 08:20 UTC.

An access-restricted HTTP 403 response was recorded on Nov 22, 2026 at 11:59 UTC. Latest classified outcome: protected; cause cloudflare challenge; mechanism challenge; observed actor Cloudflare on Nov 22, 2026 at 10:59 UTC. Registration records for the domain list PDR Ltd. as the registrar and Nov 16, 2026 as the creation date. Registration preceded first observation by 5 days. At collection time, the hostname resolved to 104.21.27.174 on AS13335 (Cloudflare, Inc.). The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. DOM analysis on Nov 21, 2026 at 19:20 UTC returned 15/100. The evidence archive retains 5 visual captures from PhishDestroy, URLScan, and Cloudflare Radar; the captures preserve the landing-page appearance. TLS metadata lists YE2 as the certificate issuer with validity through Feb 14, 2027.

Source evidence 3 sources

URLScan

Page capture

SHA-256 02d9858a…03c2d84

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

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

UUID
01a1ff23-40c7-72d5-86ab-ff1642773440
Score
0
Malicious
✗
Result at
2026-11-22T04:30:20Z
Enriched at
2026-11-22T09:13:25Z
Source timestamps
Urlscan result at: 2026-11-22 05:30:20; Urlscan enriched at: 2026-11-22 10:13:25

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-21 19:20 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-21T19:20:07Z
Source timestamp
2026-11-21 20:20:07

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

Collected source details

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

Every stored field, with its source and date
VirusTotalOriginal source recordObserved: 13 fields
Open complete records
Website checksOriginal source recordRetrieved: 16 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Crawler rules

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

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

DNS servers

Nameservers
  • IP address
    162.159.38.107
    Host
    margaret.ns.cloudflare.com
  • IP address
    173.245.59.238
    Host
    thomas.ns.cloudflare.com
DNS zone
gethelpp.top

Page quality

Layout shift (CLS)
0.003
SEO score
45
Speed Index, s
2.26
First Contentful Paint (FCP), s
0.76
Largest Contentful Paint (LCP), s
0.76
Total Blocking Time (TBT), ms
357.6
Performance score
92
Accessibility score
93
Best practices score
96

Location

IP address
2606:4700:3030::ac43:a999
ASN
13335
Organization
Cloudflare, Inc.
City
San Francisco
Country
US

TLS certificate

Subject alternative names
  • *.gethelpp.top
  • gethelpp.top
Key size, bits
256
Certificate chain
  • gethelpp.top
  • YE2
  • Root YE
  • ISRG Root X2
  • ISRG Root X1
Issuer
Let's Encrypt / YE2
Serial
05FD424E29ECF5955606BFCFA486B1BA87B9
SHA-256
a6359bd56a842313bd1f916cb21bc8987f0b3373c04dba8aca5e32fc978f1f50
Subject
gethelpp.top
Valid until
Valid from

DNS records

A
  • 172.67.169.153
  • 104.21.27.174
NS
  • margaret.ns.cloudflare.com
  • thomas.ns.cloudflare.com
SOA
Primary nameserver
margaret.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2420317510
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:3030::ac43:a999
  • 2606:4700:3037::6815:1bae

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:3037::6815:1bae
IP version
6

Technology stack

Technologies
  • AngularJS
  • Cloudflare Turnstile
  • Cloudflare
  • HTTP/3

Registration record

Registrar
PDR Ltd
Registrar IANA ID
303
Registrar URL
http://publicdomainregistry.com
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • margaret.ns.cloudflare.com
  • thomas.ns.cloudflare.com
DNSSEC
unsigned

HTTP headers

Response headers
Server
cloudflare
Content-Type
text/html; charset=UTF-8
Content-Security-Policy
default-src 'none'; script-src 'nonce-ENGnhc7YEmuYyZbPm0to9k' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenge
X-Frame-Options
SAMEORIGIN
X-Content-Type-Options
nosniff
Referrer-Policy
same-origin
Permissions-Policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
Cross-Origin-Opener-Policy
same-origin
Cross-Origin-Resource-Policy
same-origin
Cross-Origin-Embedder-Policy
require-corp
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
Crawler rules
Allow: /; Agents: *, Amazonbot, Applebot-Extended, Bytespider, CCBot; Present: ✓; Disallow: /
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
DNS server
NS: (IP: 162.159.38.107; Host: margaret.ns.cloudflare.com), (IP: 173.245.59.238; Host: thomas.ns.cloudflare.com); Zone: gethelpp.top
Quality
Cls: 0.003; Seo: 45; Si s: 2.26; Fcp s: 0.76; Lcp s: 0.76; Tbt ms: 357.6; Performance: 92; Accessibility: 93; Best practices: 96
Location
IP: 2606:4700:3030::ac43:a999; ASN: 13335; Org: Cloudflare, Inc.; City: San Francisco; Country: US
SSL
San: *.gethelpp.top, gethelpp.top; Bits: 256; Chain: gethelpp.top, YE2, Root YE, ISRG Root X2, ISRG Root X1; Issuer: Let's Encrypt / YE2; Serial: 05FD424E29ECF5955606BFCFA486B1BA87B9; SHA256: a6359bd56a842313bd1f916cb21bc8987f0b3373c04dba8aca5e32fc978f1f50; Subject: gethelpp.top; Valid to: 2027-02-14T11:24:20Z; Valid from: 2026-11-16T11:24:21Z
DNS records
A: 172.67.169.153, 104.21.27.174; NS: margaret.ns.cloudflare.com, thomas.ns.cloudflare.com; Soa: Nsname: margaret.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2420317510; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2606:4700:3030::ac43:a999, 2606:4700:3037::6815:1bae
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2606:4700:3037::6815:1bae; Family: 6
Tech stack
Technologies: AngularJS, Cloudflare Turnstile, Cloudflare, HTTP/3
Registration record
Registrar: PDR Ltd; Registrar iana ID: 303; Registrar URL: http://publicdomainregistry.com; Created: 2026-11-16T11:54:22Z; Updated: 2026-11-16T12:17:00Z; Expires: 2027-11-16T11:54:22Z; Status: clientTransferProhibited https://icann.org/epp; Nameservers: margaret.ns.cloudflare.com, thomas.ns.cloudflare.com; Dnssec: unsigned
HTTP headers
Headers: Server: cloudflare; Content type: text/html; charset=UTF-8; Content security policy: default-src 'none'; script-src 'nonce-ENGnhc7YEmuYyZbPm0to9k' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenge; X frame options: SAMEORIGIN; X content type options: nosniff; Referrer policy: same-origin; Permissions policy: accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*; Cross origin opener policy: same-origin; Cross origin resource policy: same-origin; Cross origin embedder policy: require-corp

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (5)

All capture links and hashes (5)
TLS Certificate
Issued by YE2 · stored validity ends in 83 days

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 72 report ↗
IP Context Canada104.21.27.174 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar PDR US(US)
RegistrationCreated 2026-11-16 (6d · Brand New!) — Expires 2027-11-16
Registrant countryUnited States VirusTotal WHOIS
Registrant1b15b00c7698cdf53432650ec337c945s@ VirusTotal WHOIS
HTTP Status403 Forbidden
Technical detailsProvenance & timestamps
First Detected2026-11-21
DOM Analysisanalyzed 2026-11-21score 15/100
Submitted URLhttps://gethelpp.top/
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.27.174
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

  • margaret.ns.cloudflare.com
  • thomas.ns.cloudflare.com

SOA

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

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
YE2
Valid from
2026-11-16 11:24:21
Valid until
2027-02-14 11:24:20
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinta6359bd56a842313bd1f916cb21bc8987f0b3373c04dba8aca5e32fc978f1f50
Certificate names · 2 SANs
  • *.gethelpp.top
  • gethelpp.top

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 11:59 UTC

The site was reachable but behind an access challenge at the latest check.

Technical details
Primary outcome Reachable but protected reason: Cloudflare Challenge 85% confidence
Attribution Cloudflare mechanism: Challenge source: Current Http Probe
Evidence layers Availability: Reachable but protected DNS: Resolved
Latest HTTP observation Reachable but protected Cloudflare Challenge Cloudflare Challenge 85% 2026-11-22 11:59 UTC
RDAP registration
Observed timeline last reachable: 2026-11-22 11:59 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 2 identified
Open complete records
PageSpeed (mobile): 92

Google PageSpeed Insights — mobile performance audit of gethelpp.top ·

92
Good
Performance
FCP
0.76 s
First Contentful Paint
LCP
0.76 s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
358 ms
Total Blocking Time
SI
2.26 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 403
Requested URL: https://gethelpp.top/
Just a moment...
Response
HTTP 403
HTML body
5.5 KB
Compressed
3.2 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
CF-Mitigated: challenge
Server: cloudflare
Content-Encoding: gzip
Security headers present
Content-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsReferrer-PolicyPermissions-PolicyCross-Origin-Opener-PolicyCross-Origin-Resource-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 24
Accept-CH
Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,
Alt-Svc
h3=":443"; ma=86400
Cf-Mitigated
challenge
CF-RAY
a5e166219ffabd33-AMS
Connection
close
Content-Encoding
gzip
Content-Security-Policy
default-src 'none'; script-src 'nonce-5USQdOD0HosEgjwx25AyPR' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blo
Content-Type
text/html; charset=UTF-8
Critical-Ch
Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,
Cross-Origin-Embedder-Policy
require-corp
Cross-Origin-Opener-Policy
same-origin
Cross-Origin-Resource-Policy
same-origin
Date
Sat, 21 Nov 2026 17:26:21 GMT
NEL
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Origin-Agent-Cluster
?1
Permissions-Policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
Referrer-Policy
same-origin
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=eyDvussvRojUwwdwMjD8w%2Fzhiyrulkl3%2BHvUQEQIDDBkU0yuhE6QuIUIDiFSXlshkJ215ZnCMjQjDJYsO9dUvE4a6oLPqrsNbPmdN1B5mCZUvKi59rYuqDUt5dOmUh4%3D"}]}
Server
cloudflare
Server-Timing
chlray;desc="a5e166219ffabd33"
Speculation-Rules
"/cdn-cgi/speculation"
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN

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

Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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

All stored data108
Open complete records

Captured network requests

Network requests: 21 SHA-256 hashes: 15 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-21 17:26 UTC.

Open this scan on URLScan 01a1ff23-40c7-72d5-86ab-ff1642773440 ↗

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

    Behind a check page or access restriction

    Cloudflare check page · Cloudflare · check page

  2. Domain monitor · First collection record

    Reachable

All retained availability observations4
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. 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
  • Threat Ingested
    gethelpp.top detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Forensic Evidence Collected · Technical Analysis Recorded recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: PDR Ltd. d/b/a PublicDomainRegistry.com. Abuse contacts: 1.
    • abuse-contact@publicdomainregistry.com
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

3 entries

Lifecycle

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

Reported 5 d 5 h after registration

  1. Abuse report sent

    PD-630216BA8CDC3AEF5CF6 · Receipt 85509

    abuse-contact@publicdomainregistry.com
    +2 min
  2. Added to PhishDestroy

    gethelpp.top

    same minute
  3. URLScan

    Page captured

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.

gethelpp.top

Evidence & External Reports

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

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

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

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

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

FTC ReportFraud United States

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including gethelpp.top)
  • 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.

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/gethelpp.top"
  title="PhishDestroy threat report for gethelpp.top"
  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>