VirusTotal
3 / 91 engine detections
보고서 열기피싱: lastdraftsec.online — 콘텐츠를 사용할 수 없음. 증거 요약: VirusTotal 3/91 (alphaMountain.ai, Fortinet, SOCRadar); URLQuery 1 alert; Spamhaus DBL_SPAM; PhishDestroy…
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
3 / 91 engine detections
보고서 열기1 threat-system alert
보고서 열기DBL_SPAM
no community references
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | lastdraftsec.online |
malicious | Sinkholed |
PhishDestroy threat report
Analysis indicates that the domain lastdraftsec.online was registered through Namecheap Inc on June 09, 2026. The authoritative name servers are a.dnspod.com, b.dnspod.com, and c.dnspod.com, a configuration frequently observed in short‑lived malicious deployments because DNSPod services allow rapid updates and easy domain turnover. The domain resolves to the IPv4 address 158.94.211.169; no additional hosting details such as ASN or geographic location are disclosed in the available data. Reputation services have flagged the domain: PhishDestroy lists it as blocked, and it appears on one external security blocklist, indicating that at least one downstream filter has identified it as malicious.
VirusTotal reports that the domain was scanned by 91 antivirus and URL‑reputation engines, none of which generated a detection at the time of analysis. While the absence of detections does not constitute proof of safety, it suggests that the payload or landing page may be newly observed or employing evasion techniques that have not yet triggered signatures. No SSL/TLS certificate information, HTTP status codes, page title, or content snapshots are present, leaving the visual and functional characteristics of the site unknown.
Consequently, the primary evidence supporting a risk assessment consists of the recent creation date, the use of DNSPod name servers, the blocklist entries, and the classification as a generic phishing campaign. Defenders should consider proactively blocking lastdraftsec.online and its resolving IP address at perimeter and DNS filtering layers, monitoring for any related indicators of compromise, and updating detection rules to incorporate the observed infrastructure patterns. Continuous re‑evaluation is advised as additional telemetry, such as content hashes or observed payloads, becomes available.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
5d262ed7b5c8f0c1fef2ce93d3d989fa60a6ae518e4ee344821517838e89e15aSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of lastdraftsec.online · checked Jul 31, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://lastdraftsec.online/Content-Type: text/html; charset=utf-8Cache-Control: no-storeContent-Encoding: gzipclearno-storegzip693882text/html; charset=utf-8Fri, 31 Jul 2026 17:47:52 GMTAccept-EncodingcaptchaValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
lastdraftsec.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
접속 가능→이용 불가
접속 가능
3/91 engine detections
View sourcePD-20260731-44BF68
No threat flag
View sourcePage captured
View sourcelastdraftsec.online
View sourcePD-20260731-44BF68 Recipient: abuse@omegatech.sc Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
lastdraftsec.online)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.