Analysis of www.vote-xaman.org indicates that the domain is currently active and is being used for phishing. The site was registered on July 06, 2026 through Key-Systems GmbH and resolves to the IP address 188.114.96.3. DNS resolution is provided by Cloudflare nameservers dayana.ns.cloudflare.com and doug.ns.cloudflare.com, suggesting the infrastructure is hosted behind Cloudflare's CDN.
The domain appears on one security blocklist and has been flagged by PhishDestroy, confirming its malicious intent. VirusTotal scans show that 10 out of 91 security vendors have identified the domain as malicious, reinforcing the suspicion of phishing activity. No additional public threat intelligence sources such as Google Safe Browsing or OTX are referenced in the available data, leaving those checks unverified at this time.
The lack of publicly disclosed SSL certificate details, HTTP response codes, or page title prevents a deeper content analysis, and the exact phishing lure or targeted brand remains undefined. Defenders should block traffic to 188.114.96.3 and the domain www.vote-xaman.org at the network perimeter, update intrusion detection signatures to include the observed hostnames and nameserver patterns, and monitor for any future registrations that reuse the same registrar or Cloudflare name server configuration. Continuous re‑scanning with multi‑vendor engines is recommended to capture any changes in detection status.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-379974.invalid', port=80): Max retries exceeded with url: / (Caused by
DOM Analysisanalyzed 2026年8月7日score 88/1001 brand signal
Submitted URLhttps://www.vote-xaman.org/
Favicon Hash
ケース ID
ICANN OVERSIGHT
認定と RAA の背景
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.
Certificate fingerprint299036653c200061659ace9d845604cb2a2d7a4ba59bebe740e0d245c0db35a9Certificate names · 1 SANs
vote-xaman.org
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 01:30:55 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-23 02:11:19 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.
使用技術 · 4 identified
H
HSTS
セキュリティ
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
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.
Domain Status Transition2026-09-25 01:31:09 UTC
Domain state transitioned from alive to dead.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
14 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.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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.
(CY)
