탐지를 보고하는 보안 엔진: 6. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
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@shinjiru.com.my.
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-9BB25A
Current status
HTTP 200 at latest stored check
보고서 요약
bs2best.st — 마지막으로 알려진 활성 (HTTP 200). 사기 유형: Impersonation. 증거 요약: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar, URLQuery); URLQuery 2 det.; Spamhaus DBL_SPAM; PhishDestroy score 88/100. 등록기관: NETIM.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
The domain bs2best.st returned HTTP status 200 on 2026-10-01, per the recorded HTTP check. PageSpeed recorded a performance score of 90 on 2026-09-25.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 200 for bs2best.st. VirusTotal, checked on 2026-10-01, reported 5 detections across 91 scanners. OTX, checked on 2026-09-27, showed 4 pulses. The domain was first observed on 2026-09-25. Registration dates to 2023-12-04 with registrar NETIM, and the SSL scan on 2026-09-25 identified Let's Encrypt / YR1 as issuer.
Interpretation
The recorded sources describe different measurements: an HTTP response code, scanner detections, OTX pulses, a performance score, and catalogue inclusion. These observations were collected on separate dates, so they should be read as individual records rather than a combined verdict. The chronology from first observation through the later checks shows a sequence of measurements, not a demonstrated change in the domain.
Recommended Actions
For bs2best.st, preserve the HTTP check record and the VirusTotal result as separate items, since each documents a distinct measurement. Compare the OTX pulse record with the PhishDestroy catalogue entry in a later review, keeping their original dates attached. Retain the PageSpeed observation alongside the other records so future comparisons use the same source set.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: Captcha85% confidence
Attributionmechanism: Challengesource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedCaptchaChallenge85%2026-10-11 10:10:34 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:10:34 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.
기술 · 3 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of bs2best.st· checked Sep 25, 2026
90
Good
Performance
FCP
0.99s
First Contentful Paint
LCP
3.69s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.08s
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-26 21:14:17 UTC
VirusTotal scanner detections updated from 1 to 0. Resolved alerts: SOCRadar.
VirusTotal Detections Update2026-09-25 19:15:42 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-25 18:08:30 UTC
VirusTotal scanner detections updated from 5 to 0. Resolved alerts: CRDF, Forcepoint ThreatSeeker, SOCRadar, Webroot, alphaMountain.ai.
VirusTotal Detections Update2026-09-25 14:17:06 UTC
VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-25 03:06:13 UTC
VirusTotal scanner detections updated from 3 to 4. Added scanner alerts: CRDF.
Threat First Observed2026-09-25 00:26:03 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 101.99.93.61.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
16 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.
