탐지를 보고하는 보안 엔진: 4. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
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-04DB5F
Current status
HTTP 200 at latest stored check
보고서 요약
bssl.at — 마지막으로 알려진 활성 (HTTP 200). 사기 유형: Impersonation. 증거 요약: VirusTotal 4/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar); PhishDestroy score 81/100. 등록기관: Key-Systems.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
On 2026-10-01, bssl.at returned HTTP status 200 in a recorded check, and a PhishDestroy internal listing was also recorded. The domain was first observed on 2026-09-25, according to the same evidence set.
Recorded Evidence
The HTTP check dated 2026-10-01 recorded status 200 for bssl.at, while the first observation of the domain was dated 2026-09-25. A PageSpeed check on 2026-09-25 returned a performance score of 91, and an SSL scan on the same date identified the issuer as Let's Encrypt / YR2. VirusTotal, checked on 2026-09-30, reported 4 detections across 91 scanners. OTX, checked on 2026-09-27, recorded 4 pulses. The registrar was recorded as Key-Systems GmbH ( https://nic.at/registrar/404 ).
Interpretation
The HTTP, PageSpeed, and SSL observations share the 2026-09-25 date, while the OTX and VirusTotal checks fall on later dates, so those sources describe different moments rather than one snapshot. The PhishDestroy internal listing and the OTX pulses are separate catalogue records, and their counts should be compared only alongside the dates each was captured. Because the observation dates differ, a reader can align each source to its own timestamp instead of treating all records as simultaneous.
Recommended Actions
Retain the dated records for bssl.at so that later checks can be compared against the 2026-09-25, 2026-09-27, 2026-09-30, and 2026-10-01 observations. When reviewing bssl.at again, capture the same source fields with fresh dates and note any changes in status, score, or counts. Avoid submitting sensitive information during any review of bssl.at until the relevant records have been examined.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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:28 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:10: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
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.
Google PageSpeed Insights — mobile performance audit of bssl.at· checked Sep 25, 2026
91
Good
Performance
FCP
1.06s
First Contentful Paint
LCP
3.16s
Largest Contentful Paint
CLS
0.013
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.2s
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 09:05:27 UTC
VirusTotal scanner detections updated from 3 to 2. Resolved alerts: SOCRadar.
VirusTotal Detections Update2026-09-25 06:37:53 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-25 03:06:12 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: CRDF.
VirusTotal Detections Update2026-09-25 02:01:51 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: Forcepoint ThreatSeeker.
Threat First Observed2026-09-25 00:25:59 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 111.90.148.120.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
14 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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
