VirusTotal
11 / 92
“Agapée | Jewelry | Agapee”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@rashost.com.
The latest stored availability evidence still shows the domain reachable; 16 days 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.
agapeestudio.shop — Bilinen son aktif (HTTP 200). Marka kimliğine bürünme: Fakeshop; Dolandırıcılık türü: Impersonation. Kanıt özeti: VirusTotal 11/92 (alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker, Fortinet); URLScan malicious verdict; Spamhaus DBL_SPAM; PhishDestroy score 98/100.
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
agapeestudio.shop was recorded returning HTTP status 301 on 2026-10-01, a dated response observation from an HTTP check. The same domain also appears in the PhishDestroy internal listing, a publisher-owned catalogue entry.
On 2026-10-01, an HTTP check recorded status 301 for agapeestudio.shop. VirusTotal, checked on 2026-09-26, reported 8 detections across 91 scanners. OTX was checked on 2026-09-26 and showed 4 pulses. The PhishDestroy internal listing was recorded as present. An SSL scan on 2026-09-25 named YE2 as the certificate issuer. The domain was first observed on 2026-09-24.
The VirusTotal, OTX, and PhishDestroy records each describe separate source observations, and their differing dates mean they were not gathered at one moment. The HTTP 301 response applies only to the check performed on its recorded date rather than to every possible response from the domain. Reading the records side by side lets a reader compare what each source noted without merging their metrics into a single conclusion.
For agapeestudio.shop, preserve the PhishDestroy internal listing and the VirusTotal detection record as separate items for later review. Compare the OTX pulse entry and the HTTP check result on their own terms when tracking changes. Keep the SSL scan record available so future certificate observations can be compared against it. Retain the first-observed entry alongside these records to anchor the observation window.
Bu ana bilgisayar için saklanmış tarayıcı-karşı-tarayıcı gözlemleri ile Keitaro tarzı trafik dağıtım sistemleri için gerçek zamanlı parmak izi kontrolü.
Tarayıcı notu: alive_content: raw=ok; http=200; via=https_proxy
amos.ns.cloudflare.commillie.ns.cloudflare.comLocation describes the IP network.
5f7b9ba5c846e1918c43c221a19d5e1ba32b624dc7fa4136e716a7921b18038bSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
195.96.131.106. 13 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.
PD-20260924-72D61F Recipient: abuse@rashost.com Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
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
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