On 2026-10-01, metaext.pro returned HTTP status 502 in the recorded HTTP check, and the domain was first observed on 2026-09-18. A PhishDestroy internal listing for metaext.pro is also recorded as true, while the domain's registration date is 2026-08-21.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 502 for metaext.pro. VirusTotal, checked on 2026-09-19, reported 4 detections across 89 scanners. OTX, checked on 2026-09-19, recorded 4 pulses. The domain was first observed on 2026-09-18, the same date as the PageSpeed check, which recorded a performance score of 97. Registration occurred on 2026-08-21 with registrar Spaceship, Inc., and the SSL scan on 2026-09-18 identified the issuer as Let's Encrypt / YR1. The IP address 162.241.85.94 is associated with the United States and AS46606 Unified Layer.
Interpretation
The recorded sources describe different aspects of metaext.pro: an HTTP response, a PhishDestroy internal listing, VirusTotal detections, OTX pulses, a PageSpeed score, and registration and certificate observations. These records were collected on separate dates, so they should be compared as distinct observations rather than combined into a single conclusion. The chronology shows first observation and SSL scanning on 2026-09-18, followed by OTX and VirusTotal checks on 2026-09-19, and an HTTP check on 2026-10-01.
Recommended Actions
Preserve the PhishDestroy internal listing for metaext.pro and the VirusTotal record as separate source records. Compare the OTX record with the HTTP response record for metaext.pro in separate reviews. Retain the PageSpeed observation alongside the other records for metaext.pro so future checks can be compared against the same source set.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='metaext.pro', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated Aug 21, 2026 (51d · New)—Expires Aug 21, 2027
Time to First Unavailability9h
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 18, 2026
DOM Analysisanalyzed Sep 18, 2026score 78/1001 brand signal
Submitted URLhttps://metaext.pro/mt/
Favicon Hash
Case ID
Page Title
Not Acceptable!
Impersonates
MetaMask
TLS Certificate
Hostname coverage not recorded·
Issued by Let's Encrypt / YR1· stored validity ends in 38 days
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:00:19 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-18 13:39:54 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-18 13:39:54 UTC → 2026-09-30 16:14:55 UTC · 290.58hmidpoint estimate ≈ 2026-09-24 14:57:24 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 · 6 identified
W
WordPress
CMSBlogs
WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system.
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
CRDF
Gridinsoft
SOCRadar
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of metaext.pro· checked Sep 18, 2026
97
Good
Performance
FCP
1.05s
First Contentful Paint
LCP
1.05s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.61s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
VirusTotal Detections Update2026-09-19 15:05:00 UTC
VirusTotal scanner detections updated from 3 to 4. Added scanner alerts: Gridinsoft.
VirusTotal Detections Update2026-09-19 04:38:24 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: SOCRadar.
Domain Status Transition2026-09-18 23:02:24 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-18 22:24:31 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: CRDF.
VirusTotal Detections Update2026-09-18 17:46:46 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: alphaMountain.ai.
Threat First Observed2026-09-18 13:39:54 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 162.241.85.94.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
18 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 19, 2026
Time to First Unavailability
9 hours elapsed from detection to the first unavailable observation.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
6 evidence signal groups linked1 reports recordedContent 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.
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 →
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
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · metaext.pro
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches5
Same favicon hash or the same page title as this host.
