antibodiesincorporatedhq.shop was recorded in the PhishDestroy internal catalogue on 2026-10-03, a publisher-held listing source. A PageSpeed check on the same date returned a performance score of 88 for the domain.
Recorded Evidence
The PhishDestroy internal listing for antibodiesincorporatedhq.shop carries the date 2026-10-03. VirusTotal recorded 6 detections across 91 scanners for the domain on 2026-09-14. The PageSpeed performance score of 88 was measured on 2026-10-03.
Interpretation
The PhishDestroy catalogue entry and the VirusTotal scan result are distinct observation types, and the VirusTotal check falls on an earlier calendar date than the PhishDestroy listing and the PageSpeed measurement. The PageSpeed figure describes a technical performance metric only, while the VirusTotal record reflects scanner detections, so the sources should be read separately rather than merged.
Recommended Actions
Preserve the PhishDestroy internal listing and the VirusTotal detection record for antibodiesincorporatedhq.shop as separate source records. Compare the PhishDestroy entry against the VirusTotal record when reviewing this domain, and keep the PageSpeed measurement available as its own technical reference point.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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:33:28 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:33:28 UTClast content: 2026-10-11 10:33:28 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 antibodiesincorporatedhq.shop· checked Oct 3, 2026
88
Needs Work
Performance
FCP
2.9s
First Contentful Paint
LCP
3.05s
Largest Contentful Paint
CLS
0.01
Cumulative Layout Shift
TBT
58ms
Total Blocking Time
SI
3.91s
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-03 02:35:42 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.234.
위협 대응 Pipeline
발견
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
위협 탐지됨
antibodiesincorporatedhq.shop 탐지되어 전체 분석을 위해 대기열에 추가됨
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.
