VirusTotal
6 / 89 engine detections
فتح التقرير“Tolle Inhalte erhalten”
تصيد: get-rich-content.com — المحتوى غير متوفر (HTTP 404). ملخص الأدلة: VirusTotal 6/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar, Webroot)…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
6 / 89 engine detections
فتح التقريرchecked — no detections recorded
فتح التقرير4 community references
فتح التقريرprovider verdict: clean
فتح التقريرNo threat flag
فتح التقريرNo malicious flag
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
get-rich-content.com is an impersonation phishing page aimed at German-speaking visitors. Its page title, "Tolle Inhalte erhalten" ("Get great content"), pairs with a domain name that promises easy money. PhishDestroy first flagged it on 2026-09-16. The site went offline on 2026-09-17, and at the last check on 2026-10-19 the domain was dead, with nothing served at its root. The title names no brand, while we classified the page as impersonation.
Impersonation pages borrow the look and authority of a service the visitor already trusts. The goal is to get people to log in, submit personal details or follow instructions they would refuse from a stranger. Here the hook is a vague offer of exclusive "content" under a get-rich domain name. That bait typically leads visitors into a fake sign-in or registration step. Anyone who completes it hands over credentials or personal data, which can then be used to take over accounts or for follow-up fraud.
On 2026-09-18, VirusTotal showed 6 of 89 engines flagging the domain. Those engines were alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar, Webroot and Yandex Safebrowsing. That is a small share, but it comes from several unrelated vendors, so it is more than one scanner's opinion. The domain also appears in 4 AlienVault OTX threat pulses. PhishDestroy is the only blocklist listing it.
The domain was registered through NAMECHEAP INC on 2026-05-18, about four months before PhishDestroy detected it. That gap suggests it was registered in advance rather than launched the moment it was bought. Traffic resolved to 188.114.97.3 on Cloudflare's network, with the country listed as CA. This means the real origin server sits behind Cloudflare's proxy. The site's padlock came from a Google Trust Services WE1 certificate, which proves only that the connection was encrypted, not that the site was legitimate.
If you entered a password on this site, change it immediately wherever you have used it, and turn on two-factor authentication. Then review recent account activity and active sessions. If you submitted personal or payment details, alert your bank and watch for follow-up messages that cite what you shared. Ignore any "content" offers that promise easy income. Defenders should block the domain, search proxy and email logs for visits since 2026-05-18, and reset credentials for any users who reached it.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
aisha.ns.cloudflare.comaustin.ns.cloudflare.comLocation describes the IP network.
1c8a84210841e9b741663933901af3d23c70add1cab4c4aa24bf16e2385077f7Saved 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.
get-rich-content.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
غير معروف→inactive
http_no_content
غير معروف→inactive
http_no_content
غير معروف→inactive
http_no_content
غير معروف→inactive
http_no_content
غير معروف→inactive
http_no_content
غير معروف→inactive
http_no_content
غير معروف→inactive
http_no_content
غير معروف→inactive
http_no_content
غير معروف→inactive
http_no_content
5→6
يمكن الوصول إليه→غير متوفر
يمكن الوصول إليه
4 community references
View sourceNo threat flag
View source6/89 engine detections
View sourcePD-20260916-3F143F
Page captured
View sourceget-rich-content.com
View sourcePD-20260916-3F143F Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
إذا أدخلت بيانات اعتماد الحساب أو المعلومات الشخصية أو معلومات الدفع أو قمت بتنزيل ملف من هذا النطاق، فاتخذ إجراءً فوريًا. فيما يلي موارد لمساعدتك في الإبلاغ عن الحادث وحماية نفسك.
حدد بلدك للحصول على الاتصالات الرسمية المتعلقة بالجرائم الإلكترونية أو إنشاء مسودة شكوى →.
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 ↗
get-rich-content.com)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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
تحليل التهديدات باستخدام قائمة الحظر المخزنة، وWHOIS، وDNS، وأدلة الفحص العامة
امسح الآنأرسل النطاقات المشبوهة إلى قاعدة بيانات التهديدات الخاصة بنا — ساهم في حماية المجتمع
إبلاغتقارير التصيد الاحتيالي الأخيرة وتغييرات التوفر الملحوظة
مراقبةراقب التهديدات في الوقت الفعلي أو اعترض على هذا الإدراج إذا كنت تعتقد أنه إنذار كاذب
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.