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

getlist.forum

In short

getlist.forum is a MetaMask impersonation page detected by PhishDestroy on 2026-09-29. Risk: critical (100/100). Registrar: Registrar.eu. Status: Content unavailable. Hosting: DEDIK SERVICES LIMITED. PhishDestroy sent 1 abuse report. VirusTotal: 9/91 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“Vote”

Registrar
Registrar.eu
Resolved IP
91.92.33.241
Registered
Sep 27, 2026
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 9/91 Spamhaus DBL: DBL_SPAM Stored blocklist matches: 3 Automated brand label: MetaMask Young domain: 24 days old
Sep 29, 2026 1 Report Sent
API
This domain has been flagged as malicious
Security engines reporting a detection: 9. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
URLQuery
detections
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 9 / 91 7 sources

VirusTotal

9 / 91 engine detections

Open report

Spamhaus DBL

DBL_SPAM

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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

Analysis

Critical
VirusTotal
9 / 91
Page captures
10

PhishDestroy threat report

Overview

getlist.forum is an impersonation phishing page that presents itself under the plain title "Vote", posing as a voting or polling page to draw in visitors. Crypto-focused blocklists maintained by MetaMask, ScamSniffer and SEAL have listed it, which points to crypto wallet holders as the intended targets. PhishDestroy first detected it on 2026-09-29. It was still online with its phishing content live on 2026-10-19.

How the scam works

Scams built on a "Vote" page typically copy a project's governance, community poll or giveaway vote and ask the visitor to log in or connect a wallet before they can take part. The voting step is only a pretext. Whatever the victim hands over, whether credentials, a recovery phrase, a wallet signature or a token approval, goes to the operators. Once they have it, they can take over accounts or move funds out of the connected wallet.

Evidence

On 2026-09-30, 9 of 91 VirusTotal engines flagged the domain, including alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. That is a modest count, but it comes from a mix of established antivirus vendors and threat-intel feeds. Inclusion on the MetaMask, ScamSniffer and SEAL lists carries more weight for crypto users, because those lists protect wallets directly. Spamhaus also lists the domain in its DBL under the spam category.

Infrastructure

The domain was registered through Registrar.eu on 2026-09-27, two days before PhishDestroy caught it, which fits a site set up for a short, targeted campaign. It is hosted in Germany on the DEDIK SERVICES LIMITED network. The site uses a free Let's Encrypt certificate, so the padlock in the browser says nothing about whether the page is legitimate.

What to do

Do not vote, log in or connect a wallet on getlist.forum. If you entered a password there, change it everywhere you reuse it and turn on app-based 2FA. If you typed a seed phrase, treat that wallet as compromised and move any remaining assets to a new one immediately. If you connected a wallet or signed anything, review and revoke token approvals with a trusted approval-checker and watch for unexpected transactions. Defenders should block the domain at DNS and proxy level and report it to the registrar and the hosting provider.

Collected source details

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

URLScan · 2026-09-29T01:33:57Z

Observed: · Retrieved:

Uuid
01a0eacb-f3c6-7561-b56f-472b8fb444cd
Final url
https://getlist.forum/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://getlist.forum/",
        "from": "http://getlist.forum/",
        "status": 307
    }
]
Ip
91.92.33.241
Contacted domains
[
    "coinmarketcap.com"
]
Contacted IP addresses
[
    "3.174.46.81",
    "91.92.33.241"
]
Asns
[
    "16509",
    "207043"
]
Countries
[
    "US",
    "DE"
]
Document hash
0490aba0a5f7f69806a8d1df23eda36d442aa39d4811b33de0647ee2e5f43b0b
Globals
[
    "requestResize"
]
Tls
{
    "san": [
        "getlist.forum"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR1",
    "subject": "getlist.forum",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-26T17:12:51Z",
    "valid_from": "2026-09-27T17:12:52Z"
}
Domain age days
1
Apex age days
1
Tls age days
1
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 94,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "SimpleHTTP/0.6 Python/3.10.12",
    "content-type": "text/html; charset=utf-8"
}
Cloudflare Radar · 2026-09-29T01:29:46Z

Observed: · Retrieved:

Uuid
601ef6cc-7912-4522-8ad8-bc67de9f633e
Final url
https://getlist.forum/
Status
200
History
[
    {
        "url": "https://getlist.forum/",
        "status": 200
    }
]
DOM structure hash
fa151566b5b2b76a94921867a304b9380f08a5ada4e30efdfa28788f3bffbe89
Document hash
0490aba0a5f7f69806a8d1df23eda36d442aa39d4811b33de0647ee2e5f43b0b
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "getlist.forum",
        "type": "A",
        "value": "91.92.33.241"
    }
]
Dnssec valid
false
Ip
91.92.33.241
Registration record
{
    "registrar": "Registrar.eu",
    "created": "2026-09-27T18:03:25Z",
    "updated": "2026-09-27T18:03:30Z",
    "expires": "2027-09-27T18:03:25Z",
    "nameservers": [
        "khloe.ns.cloudflare.com",
        "neil.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-21T06:41:31Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 10,
    "suspicious": 2,
    "undetected": 34
}
Vendor labels
{
    "CRDF": "malicious",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "malicious",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "alphaMountain.ai": "Spam, Newly Registered (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Registrar
Registrar.eu
Created
2026-09-27T18:03:25Z
Expires
2027-09-27T18:03:25Z
Updated
2026-09-27T18:03:30Z
First seen
2026-09-27T18:20:45Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "neil.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "khloe.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "khloe.ns.cloudflare.com"
    },
    {
        "ttl": 60,
        "type": "A",
        "value": "91.92.33.241"
    }
]
Dns at
2026-10-17T17:07:13Z
Jarm
2ad2ad0002ad2ad00042d42d00000051af7d8070a18e002eaaedf620fa118c
Certificate
{
    "san": [
        "getlist.forum"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "5ae3a6fb97943f1899dc8d454e14ab1269d",
    "sha256": "6a9e971b6e8ad41bf48da823411a2f53fdcfb5104f1dedbcb4319ff78577b535",
    "subject": "getlist.forum",
    "valid_to": "2026-12-26T17:12:51Z",
    "valid_from": "2026-09-27T17:12:52Z"
}
Registration record
{
    "registrar": "Registrar.eu",
    "registrar_iana_id": "1647",
    "registrar_url": "www.registrar.eu",
    "created": "2026-09-27T18:03:25Z",
    "updated": "2026-09-27T18:03:30Z",
    "expires": "2027-09-27T18:03:25Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "khloe.ns.cloudflare.com",
        "neil.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-09-27T18:03:25Z",
        "registration": "2026-09-27T18:03:25Z",
        "registrar expiration": "2027-09-27T18:03:25Z",
        "last update of RDAP database": "2026-10-17T15:16:00Z"
    }
}

Questions about getlist.forum

Is getlist.forum legit?

No. PhishDestroy classifies getlist.forum as a MetaMask impersonation page (risk: critical, 100/100); it was first detected on 2026-09-29. VirusTotal: 9/91 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is getlist.forum safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on getlist.forum. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used getlist.forum?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesMetaMask · ScamSniffer · PhishDestroy · SEAL 4
MetaMask Listed View source
ScamSniffer Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 10 captures

Observed page title
Vote
Automated brand references
Coinmarketcap
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 64 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 2/100 1 report Open Proxy checked Sep 29, 2026
Registrar Registrar.eu (Unknown)
Abuse contactabuse@dedik.io
RegistrationCreated Sep 27, 2026 (24d · Very New!) — Expires Sep 27, 2027
Time to First Unavailability 21 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 29, 2026
DOM Analysisanalyzed Oct 9, 2026score 90/1001 brand signal
Submitted URLhttp://getlist.forum/
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

Resolved IP
91.92.33.241
Network ASN
AS207043
Organization
Dedik Services Limited
Observed location
Frankfurt am Main, DE
Server header
SimpleHTTP/0.6 Python/3.10.12

Nameservers 2

  • khloe.ns.cloudflare.com
  • neil.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-09-27 17:12:52
Valid until
2026-12-26 17:12:51
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-09 13:03:39 UTC
Collection source
PhishDestroy collector
Certificate fingerprint6a9e971b6e8ad41bf48da823411a2f53fdcfb5104f1dedbcb4319ff78577b535
Certificate names · 1 SAN
  • getlist.forum

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-10-21 14:53:36 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-21 01:21:11 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-19 01:51:34 UTC last content: 2026-10-19 01:51:34 UTC current episode first observed: 2026-10-20 08:21:37 UTC observed RIP window: 2026-10-19 01:51:34 UTC → 2026-10-20 08:21:37 UTC · 30.50h midpoint estimate ≈ 2026-10-19 17:06:35 UTC · precision medium · 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.
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

9 / 91 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 2 detections
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
SOCRadar

Archived Evidence

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

Google PageSpeed Insights — mobile performance audit of getlist.forum · checked Sep 29, 2026

100
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
0.77s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.77s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details9

Availability observations

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

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

Stored observation history20

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Reachable→Unavailable

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 15
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  14. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  15. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    9/91 engine detections

    View source
  3. Abuse report sent

    PD-20260929-D30D6B

    abuse@dedik.io
  4. URLScan

    Page captured

    View source
  5. Added to PhishDestroy

    getlist.forum

    View source

Lookalike domains

79 stored lookalike domains

Show all (67)
metasmask.io insertion Internal report metramask.io insertion Internal report mewtamask.io insertion Internal report mmetamask.io homoglyph Internal report mtamask.io omission Internal report mwetamask.io insertion Internal report nmetamask.io homoglyph Internal report metamark.io bitsquatting Internal report metamaskj.io addition Internal report metammask.io homoglyph Internal report metamnask.io homoglyph Internal report emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Check for cloaking

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

getlist.forum

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260929-D30D6B Recipient: abuse@dedik.io
Page title stored with report: Vote
PDF notice generated
Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Content unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

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

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

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

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

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

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