탐지를 보고하는 보안 엔진: 12. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.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.
Elapsed since first report
16 days
Reports sent
1
Latest case ID
PD-20260925-0A7460
Current status
HTTP 200 at latest stored check
보고서 요약
ahavahq.shop — 마지막으로 알려진 활성 (HTTP 200). 브랜드 사칭: Fakeshop; 사기 유형: Impersonation. 증거 요약: VirusTotal 12/92 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker); URLQuery 2 det.; URLScan malicious verdict; PhishDestroy score 100/100. 등록기관: Dynadot.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
On 2026-10-01, ahavahq.shop returned an HTTP status 301 according to a recorded check, indicating a redirection at that time. The domain was first observed on 2026-09-25, providing a clear starting point for its recorded activity.
Recorded Evidence
VirusTotal recorded 10 detections out of 91 scanners for ahavahq.shop on 2026-09-28. The domain appeared in the PhishDestroy internal listing, and OTX noted 4 pulses on 2026-09-27. The SSL certificate issued by Let's Encrypt / YE1 was scanned on 2026-09-25, and the registrar is Dynadot Inc. with a registration date of 2026-05-05.
Interpretation
The evidence from PhishDestroy, OTX, and VirusTotal was collected on different dates, so each reflects a separate point in time. This means that changes in the domain's status or security profile may not be captured by a single source or observation, and comparisons should account for these timing differences.
Recommended Actions
For ahavahq.shop, retain all dated records from each source to enable future comparison and review. When assessing subsequent observations, always reference the original dates and values to track changes. Avoid submitting sensitive information to ahavahq.shop during review, and ensure evidence from each source is preserved for ongoing analysis.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
DOM Analysisanalyzed 2026년 10월 9일score 98/1001 brand signal
Submitted URLhttps://ahavahq.shop/
Favicon Hash
사건 ID
ICANN OVERSIGHT
인증 및 RAA 상황
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-11 10:11:39 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:11:39 UTClast content: 2026-10-11 10:11:39 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
기술 · 1 identified
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Google PageSpeed Insights — mobile performance audit of ahavahq.shop· checked Sep 25, 2026
66
Needs Work
Performance
FCP
2.91s
First Contentful Paint
LCP
9.58s
Largest Contentful Paint
CLS
0.01
Cumulative Layout Shift
TBT
208ms
Total Blocking Time
SI
3.15s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
VirusTotal Detections Update2026-09-25 14:17:14 UTC
VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-25 09:01:16 UTC
VirusTotal scanner detections updated from 5 to 4. Resolved alerts: SOCRadar.
VirusTotal Detections Update2026-09-25 05:55:01 UTC
VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-25 00:15:58 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 23.252.79.175.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in 웨이백 머신 — historical evidence archived
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
How we investigate & report
Public scans, evidence and abuse channels
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
