VirusTotal
18 / 89 engine detections
فتح التقرير“saffron-forest”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
تصيد: saffron-forest.com — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 18/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
18 / 89 engine detections
فتح التقرير5 threat-system alerts
فتح التقريرضار
فتح التقرير5 community references
فتح التقريرNo threat flag
فتح التقريرNo malicious flag
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DigiCert UltraDNS | saffron-forest.com |
malicious | Sinkholed |
| Cloudflare DNS | saffron-forest.com |
malicious | Sinkholed |
| DNS4EU | saffron-forest.com |
malicious | Sinkholed |
| Quad9 DNS | saffron-forest.com |
malicious | Sinkholed |
| OpenDNS | saffron-forest.com |
phishing | Phishing Block |
PhishDestroy threat report
saffron-forest.com is an impersonation phishing page: a site built to pass itself off as a service people already trust so they lower their guard and type in private details. PhishDestroy first saw it on 2026-09-15. It went offline the next day, 2026-09-16, and when checked again on 2026-10-19 the site was dead, with its content blocked at the provider level. Its page title was simply "saffron-forest", which names no brand, even though we classify the site as impersonation.
Impersonation pages copy the look, wording and login flow of a real service, then send links to the copy through ads, messages or search results. A visitor who believes they are on the genuine site enters a password, a one-time code or other account details, and that information goes straight to the operators. With it, they can take over the real account, drain balances held there, or reuse the credentials elsewhere. A bland title like "saffron-forest" does nothing to warn a visitor, which is why the page itself, not its label, is what matters.
On 2026-09-17, 18 of 89 VirusTotal engines flagged the domain as malicious. Those flags came from vendors including BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF, CyRadar and Chong Lua Dao. Several of these vendors feed browser and endpoint protection, so their agreement is meaningful. The domain also appears in five AlienVault OTX threat pulses, which means other researchers tracked it independently, and it is listed on the PhishDestroy blocklist.
The domain was registered through NAMECHEAP INC on 2026-06-15, three months before it was detected. A domain that sits unused for months and is then switched on is a common pattern, because a domain that is not brand-new draws less suspicion from filters. The site was served through Cloudflare, Inc. on an address located in Canada. Cloudflare sits in front of the real server, so its hosting address does not reveal where the operators actually were.
If you entered a password on saffron-forest.com, change it now on the genuine service and on any other account that uses the same password. Turn on app-based or hardware two-factor authentication, and review recent logins and connected devices for sessions you do not recognize. If you entered a one-time code or payment details, contact the affected provider or your bank and watch closely for unauthorized activity. Defenders should block the domain, search proxy and DNS logs for anyone who visited between 2026-09-15 and 2026-09-16, and reset credentials for any users who did.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
braden.ns.cloudflare.comnola.ns.cloudflare.comLocation describes the IP network.
89168f302b69f4a620e92e185d4586e9e754ff00460b30fc28ebbf3db1239d7aSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of saffron-forest.com · checked Sep 15, 2026
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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
saffron-forest.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
يمكن الوصول إليه→غير متوفر
يمكن الوصول إليه
5 community references
View sourceNo threat flag
View source18/89 engine detections
View sourcePD-20260915-8B27F2
Page captured
View sourcesaffron-forest.com
View sourcePD-20260915-8B27F2 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 ↗
saffron-forest.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.