VirusTotal
10 / 91 engine detections
Raporu aç“Valo.taxi - नकद और सवारी”
Oltalama: app.admin.blog.xyzsss.online — İçerik kullanılamıyor. Kanıt özeti: VirusTotal 10/91 (ADMINUSLabs, BitDefender, CRDF, CyRadar, Fortinet); URLQuery 1…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
10 / 91 engine detections
Raporu aç1 threat-system alert
Raporu açno community references
Raporu açprovider verdict: clean
Raporu aç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 | app.admin.blog.xyzsss.online |
malicious | Sinkholed |
PhishDestroy threat report
The domain app.admin.blog.xyzsss.online has been identified as a generic phishing site. The page title 'Valo.taxi - नकद और सवारी' suggests a potential brand impersonation, but the exact brand being impersonated is not clear. There is no specific drainer kit associated with this domain, but the content and structure indicate a phishing attempt to gather sensitive information from users.
Infrastructure analysis reveals that app.admin.blog.xyzsss.online has been flagged by 10 out of 95 security vendors on VirusTotal, indicating a moderate level of detection. The domain is registered through HOSTINGER operations, UAB, and resolves to the IP address 185.149.120.183. The domain was created on May 08, 2025, suggesting recent activity. The Gridinsoft trust score for this domain is 0/100, which is the lowest possible score, indicating a high level of suspicion. Additionally, the domain appears on 1 security blocklist and is blocked by PhishDestroy.
Currently, the domain is active and poses an elevated risk. Immediate response actions include blocking the domain at the network level and educating users about the potential dangers of visiting untrusted or flagged websites. Remaining risk is significant as the domain continues to be accessible and may be used to deploy further phishing attempts. Users should avoid interacting with this domain and report any suspicious activity to their security teams.
For the registrable domain xyzsss.online behind this subdomain, 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.
ns1.dns-parking.comns2.dns-parking.comLocation describes the IP network.
0297715993671ebd84598eadb5290f2ab18bff9841a28dbaf62d8ab9454b3a38demo.admin.assets.xyzsss.onlineSaved 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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='app.admin.blog.xyzsss.online', port=80): Max retries exceeded with url: / (Caused by NewCo
app.admin.blog.xyzsss.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
2→10
10/91 engine detections
View sourceNo threat flag
View sourceapp.admin.blog.xyzsss.online
View sourcePD-20260503-71CEDB
1 topluluk üyesi tarafından bildirildi; ilk görülme 03.05.2026
PD-20260503-71CEDB Recipient: abuse@ddos-guard.net 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 ↗
app.admin.blog.xyzsss.online)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.