archipelagohq.shop was recorded on 2026-10-07 with several security-related observations, including a VirusTotal scan and OTX pulse references. The domain was also listed in the PhishDestroy internal catalogue on that date, providing additional context for its monitoring status.
Recorded Evidence
On 2026-10-07, VirusTotal identified 9 detections out of 92 scanners for archipelagohq.shop. OTX registered 4 pulses referencing the domain on the same date. The domain was included in the PhishDestroy internal listing, and its SSL certificate was issued by Let's Encrypt / YE2 and scanned on 2026-10-07.
Interpretation
These records from VirusTotal, OTX, and PhishDestroy show that archipelagohq.shop was actively tracked by multiple security sources as of 2026-10-07. The presence of both detection and pulse data, along with an internal catalogue listing, highlights the domain's visibility within threat monitoring systems at that time.
Recommended Actions
To inform ongoing analysis, retain the VirusTotal, OTX, and PhishDestroy records for archipelagohq.shop. Compare these source records in future reviews to monitor any changes in security observations or catalogue status. Use this evidence to guide further investigation or policy decisions involving the domain.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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:08:03 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:08:03 UTClast content: 2026-10-11 10:08:03 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.
Last analyzed First positive detection Previous stored snapshot: 9 detections
alphaMountain.ai
CRDF
ESET
Forcepoint ThreatSeeker
Gridinsoft
LevelBlue
넷크래프트
SOCRadar
URLQuery
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of archipelagohq.shop· checked Oct 7, 2026
62
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
9.3s
Largest Contentful Paint
CLS
0.005
Cumulative Layout Shift
TBT
318ms
Total Blocking Time
SI
3.49s
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.
Threat First Observed2026-10-07 00:04:04 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.252.
위협 대응 Pipeline
발견
Analysis
Monitoring
10 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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
