탐지를 보고하는 보안 엔진: 22. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
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@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 28 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.
Stored evidence for iwuaawdjdwja.com: VirusTotal recorded 8 detections among 89 scanners on 2026-09-13. That ratio reproduces the stored check in its original units and is not converted into another measure. OpenPhish appear as named external blocklist observations for iwuaawdjdwja.com. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 8 detections among 89 scanners in the stored snapshot dated 2026-09-13. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-13 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
OpenPhish are recorded as named external blocklist observations for iwuaawdjdwja.com in the snapshot dated 2026-09-13. The stored OpenPhish blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains iwuaawdjdwja.com as a publisher record. That PhishDestroy record is counted separately from the OpenPhish external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed iwuaawdjdwja.com on 2026-09-13. The OpenPhish blocklist snapshot is dated 2026-09-13 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-10. A URLScan reference was stored on 2026-09-13 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
For iwuaawdjdwja.com, the registrar field records Dynadot Inc; this is kept as an exact source value. The source stores 64.89.161.140 as the observed address in this record. The registration date for iwuaawdjdwja.com is recorded as 2026-09-10. The SSL issuer is recorded as Let's Encrypt / YR1 in the snapshot dated 2026-09-13. The stored ASN observation records 205759 and Ghosty Networks LLC in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The iwuaawdjdwja.com record states that VirusTotal recorded 8 detections among 89 scanners on 2026-09-13. OpenPhish remain named blocklist observations from the snapshot dated 2026-09-13. PhishDestroy remains a separate publisher catalogue entry in the stored record. For iwuaawdjdwja.com, the registrar field records Dynadot Inc; this remains separate from the other source fields. The observed address field in this record contains 64.89.161.140. The supported conclusion is bounded to the exact stored observations for iwuaawdjdwja.com. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to iwuaawdjdwja.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain iwuaawdjdwja.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and OpenPhish blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to iwuaawdjdwja.com. The stored record does not justify extending that rule to 64.89.161.140 or to other infrastructure records.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='iwuaawdjdwja.com', port=80): Max retries exceeded with url: / (Caused by ConnectTimeoutErr
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-11 10:17:28 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-09-25 22:37:42 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
P
PHP
Programming languages
PHP is a general-purpose scripting language used for web development.
Last analyzed First positive detection Previous stored snapshot: 8 detections
alphaMountain.ai
BitDefender
Certego
CRDF
Ermes
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
카스퍼스키
LevelBlue
Lionic
MalwareURL
넷크래프트
Seclookup
SOCRadar
소포스
URLQuery
VIPRE
Webroot
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of iwuaawdjdwja.com· checked Sep 13, 2026
93
Good
Performance
FCP
2.29s
First Contentful Paint
LCP
2.37s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.31s
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.
Status Check2026-09-13 12:50:02 UTC
Telemetry event observed.
Threat First Observed2026-09-13 12:40:28 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 64.89.161.140.
위협 대응 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.
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.
