Skip to security report
goodforgrill.forum favicon
Domain security and threat intelligence

goodforgrill.forum

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

goodforgrill.forum displays an automated access check page that intercepts visitors before destination routing. Verify the connection source and avoid entering credentials or sensitive data if redirected.

Page title: “Securing access”

More about the sources
Recorded security signals

Stored VirusTotal result: 1/92 engines flagged. Malicious: 0. Suspicious: 1. Analysis time (as stored): 2026-11-20 01:45 UTC. Retrieved (as stored): 2026-11-22 05:26 UTC. Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.

VirusTotal detections: 1/92 Spamhaus DBL: spam domain Stored blocklist matches: 2 Young domain: 4 days old
Registrar
United StatesNameSilo
Resolved IP
Germany196.251.107.223Femo IT Solutions Limited
Registered
2026-11-17
First seen by PhishDestroy
2026-11-22
URLScan
Page captures
open gallery
Domain age
registered 2026-11-17 according to WHOIS
2026-11-22

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 goodforgrill.forum on 2026-11-22. Stored VirusTotal result: 1/92 engines flagged. Malicious: 0. Suspicious: 1. Analysis time (as stored): 2026-11-20 01:45 UTC. Retrieved (as stored): 2026-11-22 05:26 UTC. Listed by external blocklists: MetaMask, SEAL. Risk: critical (evidence score 76/100). Registrar: NameSilo. Status: Last known active. Hosting: Femo IT Solutions Limited. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
1 / 92
Blocklist matches
2 external + PhishDestroy list
Hosting
Germany196.251.107.223Femo IT Solutions Limited
Registrar
United StatesNameSilo
Registered
2026-11-17
Page captures
4

URLScan capture · 2026-11-22 05:24 UTC · SHA-256 4a583870…64dfe23

PhishDestroy analysis, reviewed version

Page layout and routing check

The goodforgrill.forum domain served a minimalist interface styled with soft purple gradients and rounded containers. At the top, small pill tags read "Protected Access" and "Mobile optimized" above the prominent bold headline "Securing access". Subtitle text explains, "We're checking the destination and preparing the most stable route for your current connection." Below this message, three checklist items show progress steps: "Checking access policy", "Verifying destination", and "Optimizing page delivery", accompanied by a loading progress bar. A secondary text box adds, "Still loading? Still loading? Refresh the page or switch to another network." The footer displays small text noting "Secure handoff • route validation • smart delivery", while abstract graphical buttons sit on the right side of the card layout.

Registration timeline and independent security flags

It was registered on 17 Nov 2026, 4 days before it was first reported, which establishes that the domain is newly created and lacks historical operating context. Because urlscan classified the page as malicious, 1 of 92 VirusTotal engines flagged it on 20 Nov 2026, and Cloudflare Radar rated it suspicious (New Domains, Security Risks), with Fortinet among the evaluating vendors, the address is recognized by external security platforms as warranting caution rather than operating as an established service.

Shared hosting infrastructure and operator patterns

The domain operates alongside other questionable properties, because 8 other domains on PhishDestroy's list share its IP address. Specifically, phantom-card.cc, happyelephant.click and gettw.cc present identical "Securing access" landing pages, pointing to a centralized operator deploying standardized routing templates across multiple addresses.

Source evidenceVirusTotal 1 / 92 5 sources

VirusTotal

1 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 10 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
1
Denominator
92
Vendors
Fortinet
Observed at
2026-11-20 01:45:13
Checked at
2026-11-22 06:26:25
Fetched at
2026-11-22 05:26:26

Spamhaus DBL

spam domain

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
goodforgrill.forum — Securing access routing page
AI description
goodforgrill.forum presents a securing access loading page with routing checks, flagged by urlscan, 1 VirusTotal engine and Cloudflare Radar.
AI summary
Page layout and routing check The goodforgrill.forum domain served a minimalist interface styled with soft purple gradients and rounded containers. At the top, small pill tags read "Protected Access" and "Mobile optimized" above the prominent bold headline "Securing access". Subtitle text explains, "We're checking the destination and preparing the most stable route for your current connection." Below this message, three checklist items show progress steps: "Checking access policy", "Verifying destination", and "Optimizing page delivery", accompanied by a loading progress bar. A secondary text box adds, "Still loading? Still loading? Refresh the page or switch to another network." The footer displays small text noting "Secure handoff • route validation • smart delivery", while abstract graphical buttons sit on the right side of the card layout. Registration timeline and independent security flags It was registered on 17 Nov 2026, 4 days before it was first reported, which establishes that the domain is newly created and lacks historical operating context. Because urlscan classified the page as malicious, 1 of 92 VirusTotal engines flagged it on 20 Nov 2026, and Cloudflare Radar rated it suspicious (New Domains, Security Risks), with Fortinet among the evaluating vendors, the address is recognized by external security platforms as warranting caution rather than operating as an established service. Shared hosting infrastructure and operator patterns The domain operates alongside other questionable properties, because 8 other domains on PhishDestroy's list share its IP address. Specifically, phantom-card.cc, happyelephant.click and gettw.cc present identical "Securing access" landing pages, pointing to a centralized operator deploying standardized routing templates across multiple addresses.
AI generated by
threat-v10-gemini
AI generated at
2026-11-22T05:57:06Z
Revision
9ad10b44aa86c7b5ae474ef343963e374a2a430a93e0a54956266e98bc8b4ecc
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: 20 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
2
Snapshots per day
0.23
Average page size, bytes
2677

Forms and mixed content

Third-party scripts
0

HTTP response

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

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
  • 22
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    162.159.44.246
    Host
    garret.ns.cloudflare.com
  • IP address
    173.245.58.114
    Host
    eva.ns.cloudflare.com
DNS zone
goodforgrill.forum

Page quality

Layout shift (CLS)
0.101
SEO score
90
Speed Index, s
0.89
First Contentful Paint (FCP), s
0.76
Largest Contentful Paint (LCP), s
0.76
Total Blocking Time (TBT), ms
0
Performance score
97
Accessibility score
93
Best practices score
96

Cookies

Cookies
  • Name
    iu1a8e8bc0b7ad45fbbc6844

Location

IP address
196.251.107.223
ASN
214351
Organization
Femo IT Solutions Limited
City
Frankfurt am Main
Country
DE

TLS certificate

Subject alternative names
  • goodforgrill.forum
Key size, bits
2048
Certificate chain
  • goodforgrill.forum
  • YR2
  • Root YR
  • ISRG Root X1
Issuer
Let's Encrypt / YR2
Serial
06BD629469DADEE9CEDDBF13D32F20547A00
SHA-256
ffeb7c98d53aff7bbc2b1691aa22bf191bc81d69211ad15895cdfbd7d4b960e9
Subject
goodforgrill.forum
Valid until
Valid from

DNS records

A
  • 196.251.107.223
NS
  • garret.ns.cloudflare.com
  • eva.ns.cloudflare.com
SOA
Primary nameserver
eva.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2420441222
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

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

IP lookup

IP address
196.251.107.223
IP version
4

Redirects

Redirect chain
  • https://goodforgrill.forum

Registration record

Registrar
NameSilo, LLC
Registrar IANA ID
1479
Registrar URL
www.namesilo.com
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
  • addPeriod https://icann.org/epp
Nameservers
  • eva.ns.cloudflare.com
  • garret.ns.cloudflare.com
DNSSEC
unsigned

HTTP headers

Response headers
Server
nginx/1.18.0 (Ubuntu)
Content-Type
text/html; charset=UTF-8
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
Web archive observations
Last: 2026-11-22T05:27:08Z; First: 2026-11-17T22:44:12Z; Changes: 1; Days archived: 2; Scans per day: 0.23; Avg page bytes: 2677
Forms and mixed content
Third party scripts: 0
Status
Up: ✓; Code: 200; Timings: DNS: 0; Wait: 154; Download: 0; Response ms: 295
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 22, 80, 443
DNS server
NS: (IP: 162.159.44.246; Host: garret.ns.cloudflare.com), (IP: 173.245.58.114; Host: eva.ns.cloudflare.com); Zone: goodforgrill.forum
Quality
Cls: 0.101; Seo: 90; Si s: 0.89; Fcp s: 0.76; Lcp s: 0.76; Tbt ms: 0; Performance: 97; Accessibility: 93; Best practices: 96
Cookies
Cookies: (Name: iu1a8e8bc0b7ad45fbbc6844)
Location
IP: 196.251.107.223; ASN: 214351; Org: Femo IT Solutions Limited; City: Frankfurt am Main; Country: DE
SSL
San: goodforgrill.forum; Bits: 2048; Chain: goodforgrill.forum, YR2, Root YR, ISRG Root X1; Issuer: Let's Encrypt / YR2; Serial: 06BD629469DADEE9CEDDBF13D32F20547A00; SHA256: ffeb7c98d53aff7bbc2b1691aa22bf191bc81d69211ad15895cdfbd7d4b960e9; Subject: goodforgrill.forum; Valid to: 2027-02-15T21:45:21Z; Valid from: 2026-11-17T21:45:22Z
DNS records
A: 196.251.107.223; NS: garret.ns.cloudflare.com, eva.ns.cloudflare.com; Soa: Nsname: eva.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2420441222; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 196.251.107.223; Family: 4
Redirects
Chain: https://goodforgrill.forum
Registration record
Registrar: NameSilo, LLC; Registrar iana ID: 1479; Registrar URL: www.namesilo.com; Created: 2026-11-17T22:39:06Z; Updated: 2026-11-17T22:39:08Z; Expires: 2027-11-17T22:39:06Z; Status: clientTransferProhibited https://icann.org/epp, addPeriod https://icann.org/epp; Nameservers: eva.ns.cloudflare.com, garret.ns.cloudflare.com; Dnssec: unsigned
HTTP headers
Headers: Server: nginx/1.18.0 (Ubuntu); Content type: text/html; charset=UTF-8
Network Security Intelligence Registrar context
Registrar context NameSilo
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
Review source investigation

Questions about goodforgrill.forum

Is goodforgrill.forum a legitimate routing page?

No official brand association links to this address. urlscan classified the page as malicious, 1 of 92 VirusTotal engines flagged it on 20 Nov 2026, and Cloudflare Radar rated it suspicious (New Domains, Security Risks).

Why does goodforgrill.forum show a securing access message?

The page displays generic loading checks stating "We're checking the destination and preparing the most stable route". Pages of this type often act as intermediate buffering steps before redirecting visitors elsewhere.

What should I do if I visited goodforgrill.forum?

Close the browser tab immediately and avoid clicking any links or refreshing through the interface. Since it was registered on 17 Nov 2026, 4 days before it was first reported, treat any unexpected redirections with skepticism.

Explore

Blocklist matches2 external + PhishDestroy list · MetaMask · PhishDestroy · SEAL 2
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Page captures (4)

All capture links and hashes (4)
Observed page title
Securing access
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 85 days

Domain details

Domain
IP Reputation Germany196.251.107.223 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has a low abuse score, but the domain itself is recognized as phishing. 0 reports checked 2026-11-22 last reported · outside the counted period
Registrar NameSilo US(US) PhishDestroy Investigation
RegistrationCreated 2026-11-17 (4d · Brand New!) — Expires 2027-11-17
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-22
DOM Analysisanalyzed 2026-11-22score 0/100
Submitted URLhttp://goodforgrill.forum/
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

Resolved IP
Germany196.251.107.223
Network ASN
AS214351
Organization
Femo IT Solutions Limited
Observed location
GermanyFrankfurt am Main, DE
Server header
nginx/1.18.0 (Ubuntu)

Nameservers 2

  • eva.ns.cloudflare.com
  • garret.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-11-17 21:45:22
Valid until
2027-02-15 21:45:21
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintffeb7c98d53aff7bbc2b1691aa22bf191bc81d69211ad15895cdfbd7d4b960e9
Certificate names · 1 SAN
  • goodforgrill.forum

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

Technologies · 2 identified
Open complete records

VirusTotal Analysis

1 / 92 security vendors flagged this domain
View on VT
Last analyzed
Fortinet

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

PageSpeed (mobile): 97

Google PageSpeed Insights — mobile performance audit of goodforgrill.forum ·

97
Good
Performance
FCP
0.76 s
First Contentful Paint
LCP
0.76 s
Largest Contentful Paint
CLS
0.101
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
0.87 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: http://goodforgrill.forum/
Final URL: https://goodforgrill.forum/
Securing access
Response
HTTP 200
HTML body
11.0 KB
Compressed
3.4 KB
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.18.0 (Ubuntu)
Content-Type: text/html; charset=utf-8
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 10
Cache-Control
no-store, no-cache, must-revalidate, max-age=0
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sun, 22 Nov 2026 05:26:39 GMT
Expires
0
Pragma
no-cache
Server
nginx/1.18.0 (Ubuntu)
Surrogate-Control
no-store
Transfer-Encoding
chunked

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

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.

All stored data96
Open complete records

Captured network requests

Network requests: 4 SHA-256 hashes: 4 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-22 05:26 UTC.

Open this scan on URLScan 01a201b6-2f4d-76a8-b27a-97950e775463 ↗

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 backfill
    Observation source
    Current state backfill
    Cause
    Probe inconclusive
    Availability state
    unreachable
    DNS state
    stale
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-22 06:25:09.000000
    Evidence SHA-256
    2efee797f08c090b6e934d6288bdba74e1831369279904529ded7d93625797f9
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-22 06:25:09
  2. Http observation
    Observation source
    Http observation
    Cause
    Probe inconclusive
    Availability state
    unreachable
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-22 06:25:09.000000
    Evidence SHA-256
    2efee797f08c090b6e934d6288bdba74e1831369279904529ded7d93625797f9
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-22 06:25:09

Threat Response Pipeline

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

Recorded events: 12. 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
    goodforgrill.forum detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Blocklist Detection · Registrar Context: NameSilo · Forensic Evidence Collected · Technical Analysis Recorded recorded
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

4 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+51 h 6 min
  3. Added to PhishDestroy+51 h 39 min
  1. Wayback Machine

    Page archived

    +1 min
  2. Added to PhishDestroy

    goodforgrill.forum

    same minute
  3. URLScan

    Page captured

    +51 h 39 min
  4. VirusTotal

    1/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.

goodforgrill.forum

Evidence & External Reports

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 goodforgrill.forum)
  • 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/goodforgrill.forum"
  title="PhishDestroy threat report for goodforgrill.forum"
  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>