beezerowaste.shop was referenced in the PhishDestroy internal listing on 2026-10-12, providing a dated record of its inclusion in a security catalogue. The domain also received a PageSpeed performance score on the same date.
Recorded Evidence
VirusTotal checked beezerowaste.shop on 2026-10-11, recording 7 detections out of 92 total scanners. OTX included the domain in 2 pulses as of 2026-10-12. The PhishDestroy internal listing referenced the domain on 2026-10-12. A PageSpeed performance score of 78 was measured on 2026-10-12.
Interpretation
PhishDestroy contains a listing for beezerowaste.shop, documenting its presence in the publisher's security catalogue. VirusTotal provides a measurement of detections from multiple scanners, while OTX records the domain's inclusion in community intelligence pulses. These sources offer a multi-faceted view of the domain's recognition across different monitoring tools.
Recommended Actions
Preserve the VirusTotal and OTX records for beezerowaste.shop to enable future comparison of scanner detections and intelligence pulse entries. Retain the PhishDestroy internal listing and PageSpeed performance score as reference points for subsequent reviews and ongoing monitoring.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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: StaleRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-12 10:00:33 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-12 10:00:33 UTClast content: 2026-10-12 10:00:33 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 Previous stored snapshot: 7 detections
alphaMountain.ai
BitDefender
ESET
G-Data
Gridinsoft
LevelBlue
Webroot
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of beezerowaste.shop· checked Oct 12, 2026
78
Needs Work
Performance
FCP
2.9s
First Contentful Paint
LCP
4.44s
Largest Contentful Paint
CLS
0.013
Cumulative Layout Shift
TBT
59ms
Total Blocking Time
SI
3.75s
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-12 09:03:45 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 162.222.90.29.
위협 대응 Pipeline
발견
Analysis
Monitoring
8 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.
