alaskankingcrabhq.shop returned an HTTP 301 status when checked on 2026-10-01, a recorded redirect response. The domain also appears in the PhishDestroy internal listing, and its first observation was logged on 2026-09-26.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 301 for alaskankingcrabhq.shop. VirusTotal recorded 8 detections across 91 scanners on 2026-09-29. OTX recorded 4 pulses on 2026-09-29. The PhishDestroy internal listing was recorded as true, and the first observation of the domain was on 2026-09-26. PageSpeed recorded a performance score of 89 on 2026-09-26.
Interpretation
The HTTP 301 record shows only the response observed at that check, not the full content or behavior of the domain. The PhishDestroy internal listing and the VirusTotal and OTX records are separate source observations that can be compared by their own dates. The first observation on 2026-09-26 and the later checks on 2026-09-29 and 2026-10-01 provide a short chronology for review.
Recommended Actions
Preserve the PhishDestroy internal listing record and the VirusTotal record for alaskankingcrabhq.shop as separate items. Compare the OTX record with the HTTP response record to see whether the observations align. Review the PageSpeed performance score alongside the other source records when assessing the domain.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 10:12:10 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:12:10 UTClast content: 2026-10-11 01:45:55 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 alaskankingcrabhq.shop· checked Sep 26, 2026
89
Needs Work
Performance
FCP
2.9s
First Contentful Paint
LCP
2.9s
Largest Contentful Paint
CLS
0.027
Cumulative Layout Shift
TBT
97ms
Total Blocking Time
SI
3.56s
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-28 12:02:11 UTC
VirusTotal scanner detections updated from 1 to 8. Added scanner alerts: CRDF, Forcepoint ThreatSeeker, G-Data, Gridinsoft, LevelBlue, Lionic, Netcraft.
VirusTotal Detections Update2026-09-27 11:16:07 UTC
VirusTotal scanner detections updated from 2 to 1. Resolved alerts: SOCRadar.
VirusTotal Detections Update2026-09-27 09:43:41 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-26 22:19:41 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: alphaMountain.ai.
Threat First Observed2026-09-26 02:34:39 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.247.
위협 대응 Pipeline
발견
Analysis
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.
