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.
Accreditation is a contract, not a safety certification.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:10:57 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-07-31 22:38:35 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-31 22:38:35 UTC → 2026-09-30 16:14:55 UTC · 1,457.61hmidpoint estimate ≈ 2026-08-31 07:26:45 UTC · precision very low · basis bounded
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
