Stored PhishDestroy threat listing. VirusTotal analysis stored; no vendor detections were recorded at check time. Exercise extreme caution — do not enter credentials or personal information.
mettax.vip was observed in a PhishDestroy internal listing on 2026-10-14, and this record provides a dated reference for its presence in a security catalogue. The domain was first observed on 2026-10-14, which aligns with its recent registration through GoDaddy.com, LLC.
Recorded Evidence
PhishDestroy internally listed mettax.vip on 2026-10-14. VirusTotal checked the domain on 2026-10-14, recording 0 detections out of 92 scanners. OTX pulses referenced the domain twice as of 2026-10-14. The domain was registered on 2026-10-13, and a PageSpeed performance score of 83 was recorded on 2026-10-14.
Interpretation
The PhishDestroy record documents mettax.vip as part of its internal listing, providing a catalogue entry rather than a direct detection or scan. VirusTotal’s measurement consists of a multi-scanner review, which did not record detections for this domain on the date checked. OTX records reference the domain in two pulses, showing it has been noted in external intelligence feeds. These sources together provide a snapshot of the domain’s presence in security and performance monitoring systems as of the dates recorded.
Recommended Actions
For mettax.vip, it is advisable to retain the PhishDestroy internal listing and VirusTotal scan results for future comparison. The OTX pulse references should also be preserved as part of the domain’s security review history. Continued monitoring using these sources can help track any changes or new entries over time.
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
Capture routing
Localarchived 2026-10-14 21:46:59 UTC
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated Oct 13, 2026 (1d · Brand New!)—Expires Oct 13, 2027
Technical detailsProvenance & timestamps
First DetectedOct 14, 2026
Submitted URLhttp://mettax.vip/
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.
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.
Google PageSpeed Insights — mobile performance audit of mettax.vip· checked Oct 14, 2026
83
Needs Work
Performance
FCP
2.44s
First Contentful Paint
LCP
4.06s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.39s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-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 responseHTTP 200
Requested URL:http://mettax.vip/
Final URL:https://mettax.vip/
Met tax
Response HTTP 200
HTML body 106.9 KB
Compressed 20.0 KB
Links 57 internal · 0 external
Detected technologies
jquerynginxbootstrap
Selected response headers
Server: nginx
Content-Type: text/html; charset=utf-8
Cache-Control: private
X-Powered-By: ThinkPHP
HSTS: not observedDNSSEC: not observedWAF / firewall: not observedCloaking flag: not observed
Saved response-header values · 9
Cache-Control
private
Connection
keep-alive
Content-Type
text/html; charset=utf-8
Date
Wed, 14 Oct 2026 19:46:58 GMT
Expires
Thu, 19 Nov 1981 08:52:00 GMT
Pragma
no-cache
Server
nginx
Transfer-Encoding
chunked
X-Powered-By
ThinkPHP
Values retained by the collector; long values may be shortened during collection.
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.
Threat First Observed2026-10-14 19:39:17 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 154.81.136.224.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
7 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.
OTX Community References
2 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 14, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Oct 14, 2026
Sent Report Recorded
Stored outgoing record associated with registrar GoDaddy.com, LLC, 1 abuse contact
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.
5 evidence signal groups linked1 reports recordedUnverified
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 · mettax.vip
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.
Same registrar: GoDaddy6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
(US)
