The domain drkuye.net was registered through GoDaddy.com, LLC on May 16, 2026. It resolves to the Cloudflare‑owned address 172.67.181.108 and uses the authoritative nameservers aria.ns.cloudflare.com and kurt.ns.cloudflare.com. The site presents a TLS certificate issued by Let’s Encrypt (E7) and returns HTTP 403 responses, with the visible page title “Just a moment…”. These observable attributes indicate a recent deployment that leverages Cloudflare’s CDN to obscure the true hosting environment. Infrastructure analysis shows the IP is located in Canada and is part of Cloudflare’s network, a common choice for malicious actors seeking to hide origin servers. The use of Let’s Encrypt certificates is consistent with fast‑track domain provisioning, and the 403 status suggests the front‑end may be serving a challenge page while the underlying payload remains hidden. No additional services or subdomains were identified during the lookup. Threat intelligence flags drkuye.net as a generic phishing site. The domain appears on a single security blocklist and has a Gridinsoft trust score of 0 out of 100, reflecting a high likelihood of abuse. Although VirusTotal currently reports zero detections across 95 engines, the absence of detections does not mitigate the observed malicious indicators. The domain’s risk level is listed as under investigation, and its operational status remains active as of the reporting date. Defenders should proactively block traffic to drkuye.net at perimeter and DNS filtering layers. Continuous monitoring of the associated IP address and its Cloudflare edge nodes is advised to capture any shift in payload delivery. Where possible, sinkholing the domain or redirecting requests to a safe response can reduce exposure while further forensic analysis is conducted. Updating internal threat feeds with the observed indicators will aid in early detection of downstream campaigns that may reuse the same infrastructure.
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='duplicate-disabled-218640.invalid', port=80): Max retries exceeded with url: / (Caused by
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 DetectedJun 15, 2026
DOM Analysisanalyzed Sep 19, 2026score 71/1003 brand signals
Favicon Hash
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.67.181.108
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 1
kurt.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / E7
Valid from
2026-05-15 13:07:34
Valid until
2026-08-13 13:07:33
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-05-17 08:00:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprint12e2a454c015cbafd44d5a853f1937708a8ab86a2078021eb23fba95b8b3530eCertificate names · 1 SANs
drkuye.net
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:30:54 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-23 02:12:05 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.
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.
Domain Status Transition2026-09-25 01:31:10 UTC
Domain state transitioned from alive to dead.
Threat Response Pipeline
Discovery
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
duplicate-disabled-218640.invalid detected and queued for full analysis
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 25, 2026
Time to First Unavailability
2444 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.
3 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 →
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.
(US)
