The domain securealliance.online was registered through Namecheap Inc on July 23, 2026 and remains active as of the report date, July 25, 2026. Authoritative name servers are dns1.registrar-servers.com and dns2.registrar-servers.com, indicating the registrar’s default infrastructure. DNS resolution points to the single IPv4 address 192.64.119.81. No additional hosting details such as ASN or geographic location are disclosed in the available data. Security telemetry shows the domain is associated with credential‑phishing activity.
It appears on one public blocklist and has been explicitly blocked by the PhishDestroy service, which corroborates the phishing classification. VirusTotal has recorded scans from 91 antivirus and URL‑reputation vendors; none have generated a detection at the time of analysis. Although the lack of detections does not imply benign intent, it does reflect that the sample has not triggered existing signatures. Public threat‑intel sources such as OTX, Google Safe Browsing, or similar reputation feeds do not currently list the domain, and no SSL certificate metadata, HTTP response codes, page title, or content snapshots have been published.
Consequently, the visual or functional characteristics of the site remain unknown, limiting attribution of the specific phishing lure. Given the recent creation date, active status, and confirmation by a dedicated anti‑phishing blocklist, defenders should treat securealliance.online as a high‑confidence phishing indicator. Network‑level controls should deny outbound connections to the resolved IP address 192.64.119.81, and email gateways should quarantine any messages containing URLs that resolve to this domain. Continuous monitoring of VirusTotal, blocklist updates, and any future host‑header or TLS observations is recommended to adjust the risk posture as additional evidence emerges.
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.
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:53 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-07-27 22:38:52 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-27 22:38:52 UTC → 2026-09-30 16:14:55 UTC · 1,553.60hmidpoint estimate ≈ 2026-08-29 07:26:53 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.
(US)
