탐지를 보고하는 보안 엔진: 7. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
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@aquiryn.com.
The latest stored availability evidence still shows the domain reachable; 13 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
13 days
Reports sent
1
Latest case ID
PD-20260928-660140
Current status
HTTP 200 at latest stored check
보고서 요약
tesladealer.co.za — 마지막으로 알려진 활성 (HTTP 200). 브랜드 사칭: Across; 사기 유형: Impersonation. 증거 요약: VirusTotal 7/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, Netcraft); PhishDestroy score 93/100. 등록기관: PDR.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
On 2026-10-01, tesladealer.co.za returned an HTTP status code of 200 in a recorded check. The same domain was first observed on 2026-09-28, according to the evidence set.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 200 for tesladealer.co.za. A PageSpeed check on 2026-09-28 recorded a performance score of 98. VirusTotal, checked on 2026-09-29, reported 7 detections across 91 scanners. OTX, checked on 2026-10-01, listed 4 pulses. The PhishDestroy internal listing was recorded as true, and the SSL scan on 2026-09-28 named YR1 as issuer.
Interpretation
The HTTP and OTX observations share the 2026-10-01 date, while the PageSpeed and SSL records come from 2026-09-28 and the VirusTotal record from 2026-09-29. Because these named sources were captured on different dates, a reader should compare them as separate snapshots rather than a single synchronized view. The PhishDestroy internal listing and the OTX pulses reflect catalogue entries, not a determination about the domain.
Recommended Actions
Reviewers should retain the dated records for tesladealer.co.za so later checks can be compared against the 2026-09-28, 2026-09-29 and 2026-10-01 observations. When repeating checks, record the same source names and dates to keep comparisons consistent. Avoid submitting sensitive information while reviewing tesladealer.co.za, since the recorded evidence does not establish how the site handles such data.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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:09:36 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:09:36 UTClast content: 2026-10-05 22:13: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.
위협 인텔리전스 교차 확인 · source references
ScamAdviserPublic lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
Last analyzed Previous stored snapshot: 7 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
넷크래프트
SOCRadar
desenmascara.me
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of tesladealer.co.za· checked Sep 28, 2026
98
Good
Performance
FCP
1.84s
First Contentful Paint
LCP
2.04s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.84s
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-29 18:12:11 UTC
VirusTotal scanner detections updated from 6 to 7. Added scanner alerts: Gridinsoft.
VirusTotal Detections Update2026-09-29 12:45:55 UTC
VirusTotal scanner detections updated from 4 to 6. Added scanner alerts: Forcepoint ThreatSeeker, alphaMountain.ai.
VirusTotal Detections Update2026-09-29 06:53:14 UTC
VirusTotal scanner detections updated from 3 to 4. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-29 02:10:45 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: CRDF.
Threat First Observed2026-09-28 08:43:40 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 23.153.104.17.
위협 대응 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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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.
