VirusTotal
9 / 91
“grandroyal-wolinak.website | 523: Origin is unreachable”
9 / 91
3 threat-system alerts
Reportchecked — no match recorded
23 community references
Reportprovider verdict: suspicious
Reportstored report
ReportAnalysis completed
Report12 checked — no blocks
Checked; no threat flag recorded
Report| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | grandroyal-wolinak.website |
malicious | Sinkholed |
| Hagezi Threat Feed | grandroyal-wolinak.website |
malicious | Sinkholed |
| Quad9 DNS | grandroyal-wolinak.website |
malicious | Sinkholed |
The domain grandroyal-wolinak.website was registered on April 14, 2026 through NameCheap, Inc. and is serviced by Cloudflare nameservers (chad.ns.cloudflare.com, sara.ns.cloudflare.com). DNS resolution points to the Cloudflare edge address 104.21.36.112, located in Canada, and the site serves HTTP/3 traffic over a valid Let’s Encrypt (E8) certificate. An HTTP request returns status 200 and the page title reports “523: Origin is unreachable,” indicating a possible backend error or intentional content disruption. The infrastructure appears on three independent blocklists and is actively blocked by PhishDestroy, MetaMask, and SEAL. VirusTotal scans show two of ninety‑four security vendors flag the domain, and Gridinsoft assigns a trust score of 0/100, reinforcing its malicious reputation. While the exact phishing lure or targeted brand is not disclosed in the available data, the classification as generic_phishing and the high‑risk status suggest it is being used for credential‑ harvesting or similar scams. Defenders should block the domain at network perimeter, monitor DNS logs for queries to grandroyal-wolinak.website, and enforce TLS inspection to capture any malicious payloads. Ongoing observation of the domain’s activity and correlation with threat‑intel feeds are recommended, as further details about the payload or victim profile remain unknown.
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.
status_splitcloudflareScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
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.
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.
Edge-IP reputation is not attributed to this domain.
sara.ns.cloudflare.comLocation describes the IP network.
2b2086109f78f260042a2e09fb251cb3d58696130dff4c7e780bf51386619df6Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
9 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Reported by 1 community member, first seen Apr 14, 2026
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive