VirusTotal
4 / 89
“rabby.herti9hye.beer”
herti9hye.beer — لم يتم التحقق منها. نوع الاحتيال: Impersonation. ملخص الأدلة: VirusTotal 4/89 (alphaMountain.ai, CRDF, Fortinet, SOCRadar); Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 80/100. مسجّل النطاق: NiceNIC.
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
The domain herti9hye.beer returned HTTP status 502 on 2026-10-01, a server-side error recorded at that check. Separately, the domain was first observed on 2026-09-13, and its registration date is listed as 2026-08-27 with registrar NICENIC INTERNATIONAL GROUP CO., LIMITED.
VirusTotal recorded 4 detections across 89 scanners on 2026-09-21. OTX recorded 6 pulses on 2026-09-21. The domain appears on two external blocklists, MetaMask and SEAL, as of the 2026-10-01 blocklist check. PhishDestroy holds an internal listing for herti9hye.beer, and the HTTP check on 2026-10-01 returned status 502.
The named sources describe different scopes: an HTTP response code reflects one request at one time, while blocklist and pulse entries reflect separate collection processes. Because the VirusTotal and OTX observations share a calendar date, they do not establish simultaneous measurement or direct comparability. The gap between the first observation and the later checks is a matter of record only, not evidence of a trend.
Preserve the VirusTotal and OTX records for herti9hye.beer so future checks can be compared against them. Retain the MetaMask and SEAL blocklist entries alongside the PhishDestroy internal listing for the same domain. Compare later HTTP responses for herti9hye.beer with the recorded status to see whether the response pattern changes.
الملاحظات المخزنة المتعلقة بالمقارنة بين برامج الزحف والمتصفح لهذا المضيف، بالإضافة إلى فحص مباشر للبصمة الرقمية لأنظمة توزيع حركة المرور على غرار «كيتارو».
ملاحظة خاصة بالماسح الضوئي: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='herti9hye.beer', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
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.
venus.ns.cloudflare.comLocation describes the IP network.
12 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.
بلاغ مجتمعي واحد
الفئةPHISHING
We are writing to report a registered domain name that is being used to publish cryptocurrency phishing pages under the names of two crypto products. The name itself is a random string with nothing behind it. A request to herti9hye[.]beer is answered with a bare "403 Forbidden"
“We are writing to report a registered domain name that is being used to publish cryptocurrency phishing pages under the names of two crypto products. The name itself is a random string with nothing behind it. A request to herti9hye[.]beer is answered with a bare "403 Forbidden" page from nginx, and the same answer comes back from meteora[.]herti9hye[.]beer when the address is typed in directly. The fraud is carried on hosts published beneath the registration — meteora[.]herti9hye[.]beer and rab”
إذا أدخلت بيانات اعتماد الحساب أو المعلومات الشخصية أو معلومات الدفع أو قمت بتنزيل ملف من هذا النطاق، فاتخذ إجراءً فوريًا. فيما يلي موارد لمساعدتك في الإبلاغ عن الحادث وحماية نفسك.
حدد بلدك للحصول على الاتصالات الرسمية المتعلقة بالجرائم الإلكترونية أو إنشاء مسودة شكوى →.
Template-based draft · optional AI wording assistance requires separate consent
تحليل التهديدات باستخدام قائمة الحظر المخزنة، وWHOIS، وDNS، وأدلة الفحص العامة
امسح الآنأرسل النطاقات المشبوهة إلى قاعدة بيانات التهديدات الخاصة بنا — ساهم في حماية المجتمع
إبلاغتقارير التصيد الاحتيالي الأخيرة وتغييرات التوفر الملحوظة
مراقبةراقب التهديدات في الوقت الفعلي أو اعترض على هذا الإدراج إذا كنت تعتقد أنه إنذار كاذب