The domain wgkkx.one was recorded on 2026-10-11 with an internal listing documented by PhishDestroy on that date. The domain is also present on two external blocklists as of the same observation.
Recorded Evidence
On 2026-10-11, PhishDestroy recorded an internal listing for wgkkx.one. On that date, the domain appeared in the MetaMask and SEAL external blocklists. The domain’s registration date with Gname.com Pte. Ltd. is 2026-09-08.
Interpretation
PhishDestroy’s listing measures the domain’s inclusion in its internal database, providing a technical indicator of assessment. The MetaMask and SEAL blocklists contain entries for wgkkx.one, which serve as external security intelligence references. These records allow for comparison of internal and external detection perspectives without implying a combined outcome.
Recommended Actions
Preserve the PhishDestroy internal listing record for wgkkx.one and the entries in the MetaMask and SEAL blocklists for ongoing review. Compare these source records to any new findings to track changes in detection status over time. Use the stored evidence to inform future security assessments and maintain a clear technical profile.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 11:19:29 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 11:19:29 UTC
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.
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-11 11:19:29 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 163.181.214.5.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
5 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
レポート 
(US)
