Security engines reporting a detection: 3. Exercise extreme caution — do not enter credentials or personal information.
Report overview
Analysis of www.facelesscoin.com shows a newly registered (21 Aug 2025) domain hosted on Vercel infrastructure and protected by an HSTS‑enabled Let’s Encrypt ce
The detailed PhishDestroy AI analysis below remains in English to preserve the original forensic record.
Analysis of www.facelesscoin.com shows a newly registered (21 Aug 2025) domain hosted on Vercel infrastructure and protected by an HSTS‑enabled Let’s Encrypt certificate (R13). The domain resolves to IP 64.29.17.65, which belongs to AS16509 Amazon.com, Inc., located in the United States. Registration was performed through GoDaddy.com, LLC and the authoritative nameservers are ns71.domaincontrol.com and ns72.domaincontrol.com. Gridinsoft assigns a trust score of 0 / 100, indicating a lack of reputable activity. The site returns HTTP 200 and advertises the page title “FACELESS COIN”. It appears on one security blocklist and is actively blocked by PhishDestroy. VirusTotal reports a single detection out of 95 scanning engines, reinforcing malicious intent. The high‑risk rating reflects the combination of a recent registration, low trust score, blocklist presence, and confirmation by multiple anti‑phishing feeds. While the exact phishing payload or credential‑harvesting page has not been publicly disclosed, the observable infrastructure strongly suggests a generic phishing operation. Defenders should block the domain at perimeter filters, monitor DNS queries for the listed nameservers, and consider adding the IP address to threat‑intel feeds. Continuous re‑evaluation is advised in case additional indicators emerge.
Detection-evasion evidence
Cloaking confirmed: scanners and visitors see different content
ObservedDifferent content was served to scanners and to visitors
The page served one response to a browser-like visitor and another to a crawler or security scanner. Cloaking exists only to keep reviewers away from the real landing page.
Stored cloaking flag
Observed
Cloaking type
content_split
Cloaking score
1/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-3163.invalid', port=80): Max retries exceeded with url: / (Caused by Ne
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, 2025 —Expires Aug 21, 2026
CloakingCloaking DetectedContent split· score 1/6
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-3163.invalid', port=80): Max retries exceeded with url: / (Caused by Ne
checked Oct 11, 2026
Time to First Unavailability196 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.
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 observationUnknownProbe Inconclusive20%2026-10-11 01:30:57 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-23 02:12:02 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.
Technologies · 2 identified
V
Vercel
PaaSCDN
Cloud platform for frontend deployment, optimized for Next.js.
H
HSTS
Security
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-3163.invalid· checked Mar 2, 2026
98
Good
Performance
FCP
0.9s
First Contentful Paint
LCP
2.25s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
22ms
Total Blocking Time
SI
2.28s
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.
Domain Status Transition2026-09-25 01:31:10 UTC
Domain state transitioned from alive to dead.
Threat Response Pipeline
Discovery
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
duplicate-disabled-3163.invalid detected and queued for full analysis
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 25, 2026
Time to First Unavailability
4695 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.
4 evidence signal groups linked0 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 →
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 matches1
Same favicon hash or the same page title as this host.
(US)
