VirusTotal
9 / 91 engine detections
Raporu aç“grandroyal-wolinak.website | 523: Origin is unreachable”
Oltalama: grandroyal-wolinak.website — Gizlenmiş · ulaşılabilir (HTTP 200). Kanıt özeti: VirusTotal 9/91 (ChainPatrol, alphaMountain.ai, BitDefender, Chong…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
9 / 91 engine detections
Raporu aç3 threat-system alerts
Raporu açSuspicious
Raporu açchecked — no match recorded
23 community references
Raporu aç12 kontrol edildi — engelleme yok
No threat flag
Raporu açNo malicious flag
Raporu açResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| 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 |
PhishDestroy threat report
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.
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 itibarı bu etki alanıyla ilişkilendirilmez.
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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
status_split · alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
grandroyal-wolinak.website
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
No threat flag
View source23 community references
View source9/91 engine detections
View sourcegrandroyal-wolinak.website
View source1 topluluk üyesi tarafından bildirildi; ilk görülme 14.04.2026
Listed domains receive at least one abuse report; this entry has no retained notification history.
Hesap kimlik bilgilerini, kişisel bilgileri veya ödeme bilgilerini girdiyseniz ya da bu alan adından bir dosya indirdiyseniz hemen harekete geçin. Aşağıda olayı bildirmenize ve kendinizi korumanıza yardımcı olacak kaynaklar bulunmaktadır.
resmi siber suç iletişim bilgileri veya şikayet taslağı oluştur → almak için ülkenizi seçin.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
grandroyal-wolinak.website)Tüm ayrıntıları bilmeseniz bile — yine de şikayette bulun. Kısmi bilgiler de soruşturmalara yardımcı olmaktadır.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Saklanan engelleme listesi, WHOIS, DNS ve genel tarama kanıtlarını kullanarak tehdit analizi
Şimdi TaraŞüpheli alan adlarını tehdit veritabanımıza bildirin — topluluğu koruyun
BildirSon kimlik avı raporları ve gözlemlenen kullanılabilirlik değişiklikleri
İzleCanlı tehditleri izleyin veya bunun yanlış bir uyarı olduğunu düşünüyorsanız bu kayda itiraz edin
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.