Skip to security report
t-proka.com favicon
Domain security and threat intelligence

t-proka.com

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

PhishDestroy first recorded t-proka.com on 2026-09-04. Stored VirusTotal result: 9/92 engines flagged. Malicious: 7. Suspicious: 2. Analysis time (as stored): 2026-10-11 22:07 UTC. Retrieved (as stored): 2026-10-23 03:51 UTC. Listed by external blocklists: MetaMask, SEAL.

Page title: “T-Pro”

More about the sources
Recorded security signals

Stored VirusTotal result: 9/92 engines flagged. Malicious: 7. Suspicious: 2. Analysis time (as stored): 2026-10-11 22:07 UTC. Retrieved (as stored): 2026-10-23 03:51 UTC. Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.

VirusTotal detections: 9/92 Stored blocklist matches: 2
Registrar
Realtime
Resolved IP
United States104.21.76.155Cloudflare, Inc. · CDN
Registered
2026-07-20
First seen by PhishDestroy
2026-09-04
OTX
community references
Page captures
open gallery
Domain age
registered 2026-07-20 according to RDAP
Reports sent
view timeline
OTX: 5 refs 2026-09-04 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.

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
Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded t-proka.com on 2026-09-04. Stored VirusTotal result: 9/92 engines flagged. Malicious: 7. Suspicious: 2. Analysis time (as stored): 2026-10-11 22:07 UTC. Retrieved (as stored): 2026-10-23 03:51 UTC. Listed by external blocklists: MetaMask, SEAL. Risk: critical (evidence score 100/100). Registrar: Realtime. Status: Content unavailable. Hosting: CLOUDFLARENET - Cloudflare, Inc., US. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Content unavailable
VirusTotal
9 / 92
Blocklist matches
2 external + PhishDestroy list
Scam type (automated label)
Impersonation
Hosting
United States104.21.76.155Cloudflare, Inc. · CDN
Registrar
Realtime
Registered
2026-07-20
OTX
5 community refs
Page captures
6

PhishDestroy analysis, earlier unreviewed version

Overview

t-proka.com is an impersonation phishing page that presented itself under the name "T-Pro". MetaMask and SEAL both list it, which places its target audience among crypto wallet users. PhishDestroy first detected it on 2026-09-04. The site has been offline since 2026-09-11, and its DNS was still inactive when we last checked on 2026-10-19.

How the scam works

Impersonation pages like this one borrow the name and look of a product people already trust, here "T-Pro", so visitors relax and follow the site's prompts. In crypto-focused schemes, those prompts usually ask the visitor to log in, enter a seed phrase or private key, connect a wallet, or send funds to an account the operators control. Anything typed or signed goes straight to the attackers. A leaked seed phrase hands over the whole wallet, and a signed transaction can move assets that cannot be recovered.

Evidence

When VirusTotal scanned the domain on 2026-09-06, 11 of 90 engines flagged it. The vendors included alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. That count is modest, but the detections came from several unrelated vendors within two days of our first sighting. MetaMask's and SEAL's crypto-specific blocklists carry the domain alongside PhishDestroy, and it appears in 5 AlienVault OTX threat pulses.

Infrastructure

The domain was registered through Realtime Register B.V. on 2026-07-20, roughly six weeks before it came to our attention. That gap fits an operator who sets up domains in advance and puts them into use later. The site ran behind Cloudflare (AS13335, US), which hides the real origin server. It stopped resolving about a week after detection, a short lifespan that is common for disposable phishing domains.

What to do

If you entered a seed phrase or private key on t-proka.com, assume that wallet is compromised. Create a new wallet on a clean device and move any remaining assets to it immediately. If you connected a wallet or signed anything there, review and revoke token approvals using a trusted approval checker. If you reused a password from the site anywhere else, change it and turn on app-based 2FA. Defenders should block the domain at DNS and proxy level and add it to watchlists in case it is reactivated. They should also search logs for visits after 2026-07-20 and look for lookalike "T-Pro" domains.

Source evidenceVirusTotal 9 / 92 · OTX 5 references 6 sources

VirusTotal

9 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 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
Numerator
11
Denominator
90
Vendors
alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, SOCRadar, Sophos, VIPRE
Checked at
2026-09-06 04:12:07

OTX

5 community references

Open report
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
t-proka.com — T-Pro Impersonation Phishing Page
AI description
t-proka.com is an impersonation phishing page branded "T-Pro", blocklisted by MetaMask and SEAL for targeting crypto wallet users and investors.
AI summary
Overview t-proka.com is an impersonation phishing page that presented itself under the name "T-Pro". MetaMask and SEAL both list it, which places its target audience among crypto wallet users. PhishDestroy first detected it on 2026-09-04. The site has been offline since 2026-09-11, and its DNS was still inactive when we last checked on 2026-10-19. How the scam works Impersonation pages like this one borrow the name and look of a product people already trust, here "T-Pro", so visitors relax and follow the site's prompts. In crypto-focused schemes, those prompts usually ask the visitor to log in, enter a seed phrase or private key, connect a wallet, or send funds to an account the operators control. Anything typed or signed goes straight to the attackers. A leaked seed phrase hands over the whole wallet, and a signed transaction can move assets that cannot be recovered. Evidence When VirusTotal scanned the domain on 2026-09-06, 11 of 90 engines flagged it. The vendors included alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. That count is modest, but the detections came from several unrelated vendors within two days of our first sighting. MetaMask's and SEAL's crypto-specific blocklists carry the domain alongside PhishDestroy, and it appears in 5 AlienVault OTX threat pulses. Infrastructure The domain was registered through Realtime Register B.V. on 2026-07-20, roughly six weeks before it came to our attention. That gap fits an operator who sets up domains in advance and puts them into use later. The site ran behind Cloudflare (AS13335, US), which hides the real origin server. It stopped resolving about a week after detection, a short lifespan that is common for disposable phishing domains. What to do If you entered a seed phrase or private key on t-proka.com, assume that wallet is compromised. Create a new wallet on a clean device and move any remaining assets to it immediately. If you connected a wallet or signed anything there, review and revoke token approvals using a trusted approval checker. If you reused a password from the site anywhere else, change it and turn on app-based 2FA. Defenders should block the domain at DNS and proxy level and add it to watchlists in case it is reactivated. They should also search logs for visits after 2026-07-20 and look for lookalike "T-Pro" domains. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a06d29-7a69-7237-b945-2c355b597ff2/ VirusTotal report: https://www.virustotal.com/gui/domain/t-proka.com Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=t-proka.com Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
AI generated by
threat-anthropic
AI generated at
2026-10-19T10:23:01Z
Revision
27d7943da858ab6a085afb3cf9d5e329b08b61cc45556dd27bd330d47f1edaf4
Mode
stored
Interpretation
Earlier stored analysis, not reviewed; 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

Questions about t-proka.com

Is t-proka.com legit?

PhishDestroy rates t-proka.com as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-09-04. Stored VirusTotal result: 9/92 engines flagged. Malicious: 7. Suspicious: 2. Analysis time (as stored): 2026-10-11 22:07 UTC. Retrieved (as stored): 2026-10-23 03:51 UTC. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is t-proka.com safe to connect a wallet?

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

What should I do if I used t-proka.com?

  • 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 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 (6)

All capture links and hashes (6)
t-proka.com: Crypto scam — Blocked by MetaMask, flagged by SEAL, 11/90 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card t-proka.com: Crypto scam — Blocked by MetaMask, flagged by SEAL, 11/90 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 14f02bfe3df2

Domain details

Domain
URLScan verdict Malicious score 100 Phishing report ↗
IP Context United States104.21.76.155 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Realtime
RegistrationCreated 2026-07-20 (124d) — Expires 2027-07-20
Time to First Unavailability 6 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 Detected2026-09-04
Submitted URLhttp://t-proka.com/
Favicon Hash
Case ID
Observed page title
T-Pro
Automated brand references
MetaMask
TLS Certificate
Issued by Google Trust Services · stored validity ends in 43 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States104.21.76.155
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
United StatesSan Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • dorthy.ns.cloudflare.com
  • osmar.ns.cloudflare.com

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services
Valid from
2026-07-20 16:20:49
Valid until
2026-10-18 17:19:06
Hostname match
Yes
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprintf06e4bae4716709a5579728d2cfccd480e106e364265a54ade83cd48dfb162bd
Certificate names · 2 SANs
  • t-proka.com
  • *.t-proka.com

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-21 18: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-09-07 22:14 UTC current episode first observed: 2026-09-30 16:14 UTC observed RIP window: 2026-09-07 22:14 UTC → 2026-09-30 16:14 UTC · 546.00h midpoint estimate ≈ 2026-09-19 07:14 UTC · precision low · 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 · 5 identified
Open complete records

VirusTotal Analysis

9 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy Previous stored snapshot: 3 detections
CRDF
G-Data
Lionic
Sophos
Fortinet
SOCRadar
BitDefender
alphaMountain.ai
Forcepoint ThreatSeeker
PageSpeed (mobile): 59

Google PageSpeed Insights — mobile performance audit of t-proka.com ·

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

Availability observations

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

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

All stored data122
Open complete records

Captured network requests

Network requests: 115 SHA-256 hashes: 99 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 02:53 UTC.

Open this scan on URLScan 01a06d29-7a69-7237-b945-2c355b597ff2 ↗

Check for cloaking

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

t-proka.com
Saved result
Unreachable
Stored observation history25
Open complete records
All retained availability observations113
Open complete records

Threat Response Pipeline

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

Recorded events: 16. 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
    t-proka.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · OTX Community References · Automated brand label: MetaMask · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable · VirusTotal detections +1 recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Realtime Register B.V.. Abuse contacts: 1.
    • rtr-security-threats@realtimeregister.com
Publication & AvailabilityDestroyList Published · Content Observed Unavailable · Time to First Unavailability 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.
  • Time to First Unavailability
    Hours from detection to the first unavailable observation: 149

Recorded activity

6 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+45 d 22 h
  3. First abuse report sent+19 min
  4. VirusTotal analysis with detections+37 d 5 h

Reported 45 d 23 h after registration

  1. VirusTotal

    9/92 engine detections

    +37 d 5 h
  2. Realtime Register

    Asked for a report through its web form

    same minute
  3. Abuse report sent

    PD-20260904-05EA36 · Receipt 65451

    rtr-security-threats@realtimeregister.com
    +3 min
  4. AlienVault OTX

    5 community references

    +16 min
  5. Added to PhishDestroy

    t-proka.com

    same minute
  6. 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

Lookalike domains

79 stored lookalike domains

Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.

etamask.io Missing character Variant of metamask.io Internal report A 185.66.140.182MX etamask.ioNS ns13.knownsrv.com meetamask.io Repeated character Variant of metamask.io Internal report A 185.66.140.182MX meetamask.ioNS ns13.knownsrv.com megamask.io Replaced character Variant of metamask.io Internal report A 66.96.162.138MX alt1.aspmx.l.google.comNS ns1.domain.com metam.ask.io Split into subdomain Variant of metamask.io Internal report A 15.197.162.184 metamaak.io Replaced character Variant of metamask.io Internal report A 185.66.140.182MX metamaak.ioNS ns13.knownsrv.com metamadk.io Replaced character Variant of metamask.io Internal report A 185.66.140.182MX metamadk.ioNS ns13.knownsrv.com metamaks.io Swapped characters Variant of metamask.io Internal report A 185.66.140.182MX metamaks.ioNS ns13.knownsrv.com metamassk.io Inserted character Variant of metamask.io Internal report A 185.66.140.182MX metamassk.ioNS ns13.knownsrv.com metamsask.io Inserted character Variant of metamask.io Internal report A 185.66.140.182MX metamsask.ioNS ns13.knownsrv.com metamssk.io Replaced character Variant of metamask.io Internal report A 185.66.140.182MX metamssk.ioNS ns13.knownsrv.com metanask.io Lookalike letters Variant of metamask.io Internal report A 185.66.140.182MX metanask.ioNS ns13.knownsrv.com metanmask.io Lookalike letters Variant of metamask.io Internal report A 185.66.140.182MX metanmask.ioNS ns13.knownsrv.com

Showing 12 of 79

Show 67 more
metasmask.io Inserted character Variant of metamask.io Internal report A 185.66.140.182MX metasmask.ioNS ns13.knownsrv.com metramask.io Inserted character Variant of metamask.io Internal report A 185.66.140.182MX metramask.ioNS ns13.knownsrv.com mewtamask.io Inserted character Variant of metamask.io Internal report A 185.66.140.182MX mewtamask.ioNS ns13.knownsrv.com mmetamask.io Lookalike letters Variant of metamask.io Internal report A 185.66.140.182MX mmetamask.ioNS ns13.knownsrv.com mtamask.io Missing character Variant of metamask.io Internal report A 185.66.140.182MX mtamask.ioNS ns13.knownsrv.com mwetamask.io Inserted character Variant of metamask.io Internal report A 185.66.140.182MX mwetamask.ioNS ns13.knownsrv.com nmetamask.io Lookalike letters Variant of metamask.io Internal report A 185.66.140.182MX nmetamask.ioNS ns13.knownsrv.com metamark.io Bit flip Variant of metamask.io Internal report A 13.248.213.45MX mx0.123-reg.co.ukNS ns45.domaincontrol.com metamaskj.io Added character Variant of metamask.io Internal report A 185.66.140.182MX metamaskj.ioNS ns13.knownsrv.com metammask.io Lookalike letters Variant of metamask.io Internal report A 185.66.140.182MX metammask.ioNS ns13.knownsrv.com metamnask.io Lookalike letters Variant of metamask.io Internal report A 185.66.140.182MX metamnask.ioNS ns13.knownsrv.com emtamask.io Swapped characters Variant of metamask.io A 185.66.140.182MX emtamask.ioNS ns13.knownsrv.com m-etamask.io Added hyphen Variant of metamask.io A 104.247.81.99NS ns1.parkingcrew.net meamask.io Missing character Variant of metamask.io A 185.66.140.182MX meamask.ioNS ns13.knownsrv.com meatmask.io Swapped characters Variant of metamask.io A 185.66.140.182MX meatmask.ioNS ns13.knownsrv.com meramask.io Replaced character Variant of metamask.io A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mertamask.io Inserted character Variant of metamask.io A 185.66.140.182MX mertamask.ioNS ns13.knownsrv.com metaamask.io Repeated character Variant of metamask.io A 185.66.140.182MX metaamask.ioNS ns13.knownsrv.com metaamsk.io Swapped characters Variant of metamask.io A 185.66.140.182MX metaamsk.ioNS ns13.knownsrv.com metaask.io Missing character Variant of metamask.io A 185.66.140.182MX metaask.ioNS ns13.knownsrv.com metalmask.io Inserted character Variant of metamask.io A 15.197.148.33NS ns37.domaincontrol.com metamaask.io Inserted character Variant of metamask.io A 185.66.140.182MX metamaask.ioNS ns13.knownsrv.com metamadsk.io Inserted character Variant of metamask.io A 185.66.140.182MX metamadsk.ioNS ns13.knownsrv.com metamaek.io Replaced character Variant of metamask.io A 172.65.190.172NS expire1.gname-dns.com metamak.io Missing character Variant of metamask.io A 185.66.140.182MX metamak.ioNS ns13.knownsrv.com metamas.io Missing character Variant of metamask.io A 185.66.140.182MX metamas.ioNS ns13.knownsrv.com metamasak.io Inserted character Variant of metamask.io A 185.66.140.182MX metamasak.ioNS ns13.knownsrv.com metamasdk.io Inserted character Variant of metamask.io A 185.66.140.182MX metamasdk.ioNS ns13.knownsrv.com metamask-io.com Variant Variant of metamask.io A 13.248.169.48NS ns1.afternic.com metamasl.io Replaced character Variant of metamask.io A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com metamasm.io Replaced character Variant of metamask.io A 91.195.240.94NS ns1cnb.name.com metamsak.io Swapped characters Variant of metamask.io A 185.66.140.182MX metamsak.ioNS ns13.knownsrv.com metamsk.io Missing character Variant of metamask.io A 185.66.140.182MX metamsk.ioNS ns13.knownsrv.com metamusk.io Vowel swap Variant of metamask.io A 59.149.253.82NS ns1cnb.name.com metamzsk.io Replaced character Variant of metamask.io A 91.195.240.94NS ns1cnb.name.com metarnask.io Lookalike letters Variant of metamask.io NS ns15.domaincontrol.com metmaask.io Swapped characters Variant of metamask.io A 185.66.140.182MX metmaask.ioNS ns13.knownsrv.com metmask.io Missing character Variant of metamask.io A 207.246.78.75NS ns1.dnsowl.com metsamask.io Inserted character Variant of metamask.io A 185.66.140.182MX metsamask.ioNS ns13.knownsrv.com metsmask.io Replaced character Variant of metamask.io A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mettamask.io Repeated character Variant of metamask.io A !ServFailNS !ServFail metwmask.io Replaced character Variant of metamask.io A 44.230.85.241NS curitiba.ns.porkbun.com metyamask.io Inserted character Variant of metamask.io A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com metzmask.io Replaced character Variant of metamask.io A 91.195.240.94NS ns1cnb.name.com meyamask.io Replaced character Variant of metamask.io A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com meytamask.io Inserted character Variant of metamask.io A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mitamask.io Vowel swap Variant of metamask.io A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mnetamask.io Lookalike letters Variant of metamask.io A 185.66.140.182MX mnetamask.ioNS ns13.knownsrv.com mretamask.io Inserted character Variant of metamask.io A 185.66.140.182MX mretamask.ioNS ns13.knownsrv.com mrtamask.io Replaced character Variant of metamask.io A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com mstamask.io Replaced character Variant of metamask.io A 44.230.85.241NS curitiba.ns.porkbun.com mteamask.io Swapped characters Variant of metamask.io A 185.66.140.182MX mteamask.ioNS ns13.knownsrv.com mwtamask.io Replaced character Variant of metamask.io A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com rnetamask.io Lookalike letters Variant of metamask.io A 34.42.100.71NS ns-cloud-a1.googledomains.com matamask.io Bit flip Variant of metamask.io A 216.245.197.45NS ns1.badgerdns.com mdtamask.io Bit flip Variant of metamask.io A 91.195.240.94NS ns1cnb.name.com metamasi.io Bit flip Variant of metamask.io A 91.195.240.94NS ns1cnb.name.com metamasj.io Bit flip Variant of metamask.io A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com metamaska.io Added character Variant of metamask.io A 198.185.159.145MX alt1.aspmx.l.google.comNS ns-cloud-e1.googledomains.com metamaskk.io Added character Variant of metamask.io A 185.66.140.182MX metamaskk.ioNS ns13.knownsrv.com metamaskl.io Added character Variant of metamask.io A 185.66.140.182MX metamaskl.ioNS ns13.knownsrv.com metamaso.io Bit flip Variant of metamask.io A 44.230.85.241NS curitiba.ns.porkbun.com metamesk.io Bit flip Variant of metamask.io A 77.247.179.91NS ns1.badgerdns.com metamqsk.io Bit flip Variant of metamask.io A 91.195.240.94NS ns1cnb.name.com metemask.io Bit flip Variant of metamask.io A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com netamask.io Lookalike letters Variant of metamask.io A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com xn--metamas-bhb.io Lookalike letters Variant of metamask.io A 109.69.20.213NS aldo.ns.cloudflare.com

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260904-05EA36 Recipient: rtr-security-threats@realtimeregister.com
Page title stored with report: T-Pro
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.

  • 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
  • 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

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 t-proka.com)
  • 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/t-proka.com"
  title="PhishDestroy threat report for t-proka.com"
  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>