The owner of the website is using a service to hide their identity on WHOIS According to Tranco this site has a low rank The registrar has a high % of spammers and fraud sites This website may offer high-risk cryptocurrency services This website has received mainly negative reviews This website is (very) young.
The SSL certificate is valid This website is safe according to DNSFilter
Gridinsoft Analysis1 / 100
Hosting SSL Certificate Scam - High Risk 18+ Cryptocurrency Cryptocurrency - Risk Registration Form Casino
Network Security Intelligence Registrar context
Registrar contextNameSilo
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
This domain, dragonlord.online, was registered on September 17, 2025 through NameSilo, LLC and is currently listed as offline. The authoritative name servers are luciana.ns.cloudflare.com and logan.ns.cloudflare.com (both listed in mixed case). DNS resolution points to the Cloudflare address 188.114.97.3, which belongs to AS13335 (Cloudflare, Inc.) and is geolocated in the United States. No TLS certificate is presented for the host, indicating that the site operates without HTTPS protection.
The page title returned from the site reads "Dragonlord: Most Popular Online Crypto Casino Based on Blockchain," which aligns with the classified scam type of a crypto‑casino phishing campaign. Analysis of the content reveals the use of the publicly available "Gambler Scam" phishing kit, a tool commonly employed to lure victims into fraudulent cryptocurrency gambling platforms. Reputation services flag the domain aggressively: Gridinsoft assigns a trust score of 1 / 100, Scamadviser also reports 1 / 100, and the domain appears on a single security blocklist. PhishDestroy has actively blocked the host.
On the threat‑intelligence side, AlienVault OTX includes the domain in one pulse, and VirusTotal reports that 12 of 95 scanning engines have identified malicious behavior associated with the domain. Given the combination of a low trust score, absence of encryption, association with a known phishing kit, and detections across multiple vendors, defenders should continue to block any network traffic to 188.114.97.3 and add dragonlord.online to local deny lists. Monitoring of Cloudflare edge IPs for similar patterns is advised, as the infrastructure may be reused for future campaigns. At present, the site’s content cannot be examined directly because it is offline, so additional forensic collection is limited to DNS and passive DNS records.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='dragonlord.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedDec 16, 2025
DOM Analysisanalyzed Apr 23, 2026score 83/100
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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 inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:08:23 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-06-15 22:13:15 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-15 22:13:15 UTC → 2026-09-30 16:14:55 UTC · 2,562.03hmidpoint estimate ≈ 2026-08-08 07:14:05 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.
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.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
dragonlord.online detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
May 14, 2026
Time to First Unavailability
3564 hours elapsed from detection to the first unavailable observation.
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.
7 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · dragonlord.online
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Gridinsoft Analysis
1 / 100
(US)
PhishDestroy Investigation
