Why this matters — ICANN RAA §3.18 obligation & victim-assistance
On PhishDestroy delivered an evidence-backed abuse report
(repeated 7 times, most recently ) to domainabuse@tucows.com with VirusTotal detections, urlscan capture, legal violations, and full screenshot evidence.
More than 5 months later, the phishing infrastructure remains reachable
.
Under ICANN RAA §3.18 accredited registrars are contractually obliged to “take reasonable and prompt steps to investigate and respond appropriately to any reports of abuse.” Silence beyond 24 hours after a documented notification with verifiable evidence is not a timing issue — it is a policy decision to let the operation continue. PhishDestroy\'s position: where a registrar fails to act on clear evidence, the registrar has aligned itself with the operator of the scheme and bears co-responsibility for downstream harm caused to victims from the moment of notification onward.
Victim-assistance obligation. If Tucows Domains Inc. doesn't consider the listed detections enough proof — that is interesting in itself, given the volume of independent vendor confirmations. But after 7 separate notifications over 5 months, with the operation still active, the registrar took no measurable action to mitigate the harm caused by their client. The reasonable next step is direct help to any identified victims — contact & payment-trail disclosure, abuse-thread transcripts, registrant data preservation — since the registrar chose, by inaction, to extend the window of damage.
lucknight[.]com
lucknight.com 피싱 및 보안 점검
“Lucknight | XXX”
lucknight.com: VirusTotal 엔진 91개 중 13개가 이 도메인을 탐지했습니다. DNS, SSL, 등록기관, 차단 목록, 위협 정보를 확인하세요.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
PhishDestroy first recorded lucknight.com on Dec 16, 2025. This English evidence brief is rebuilt from the current structured observations stored for the report. The current evidence score, computed from those stored observations, is 100/100.
The latest stored availability state is “Last known active” on Aug 2, 2026 at 00:29 UTC. No conclusive HTTP response is stored, so current availability remains unverified.
VirusTotal returned 13 detections from 91 scanners in the stored check on Aug 1, 2026 at 04:22 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 2, 2026 at 00:20 UTC. PhishDestroy's own listing is excluded from that count. A zero-match snapshot is not a safety verdict.
Other stored evidence. Google Safe Browsing stored no positive flag on Mar 3, 2026 at 05:14 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 1 pulse reference on Mar 1, 2026 at 15:53 UTC. OTX pulses are community-intelligence references, not vendor verdicts. Spamhaus DBL stored the result DBL_SPAM on Jul 14, 2026 at 16:34 UTC. A URLScan capture is stored from Feb 26, 2026 at 02:19 UTC.
Stored context lists registrar Tucows Domains Inc., IP address 172.67.149.219, registration date Oct 21, 2025, apparent target Genericcrypto. Except for the registration date, these fields do not share a source timestamp in this report and may change.
Treat these as stored, time-bound observations rather than a live safety guarantee. Source verdicts and reachability can change, and zero or missing vendor matches never prove that a domain is safe. Avoid interacting with the domain while uncertainty remains, and use the appeal process if this report is inaccurate.
위협 대응 Pipeline
공개 차단 목록 상태
증거 수집
도메인 인텔리전스
기술적 세부 사항DNS, SSL SAN, 타임스탬프
ICANN OVERSIGHT
인증 및 RAA 상황
인증 및 RAA 상황
ICANN은 돈을 받았다. 책임은 끝내 오지 않았다.
이 gTLD에서 위 등록기관은 ICANN과의 계약에 따라 운영됩니다. ICANN은 등록, 갱신 및 이전과 연계된 연간 수수료, 변동 수수료 및 거래 기반 수수료를 징수합니다.
인증: 수익화 완료. 책임: 나중에 다시 확인하십시오.
그러고 나면 마법이 시작됩니다. ICANN은 RAA §3.18을 작성하고, 등록기관은 자기 고객 기반 안의 악용을 스스로 조사하며, 피해자는 증거를 공짜로 제공하는 동안 모든 단계는 다른 누군가가 움직이기만을 기다립니다. 그 덕분에 피해자가 더 안전하다고 느낀다면 훌륭합니다—청구서가 제 몫을 한 셈이니까요.
악용 신고 이력 · 7 stored reports over 105 days · click to expand
-
Report #1 Feb 8, 2026 · 18:29 UTCPhishing Abuse Report: lucknight[.]comdomainabuse@tucows.com
-
Report #2 ICANN CC 148h still active Feb 14, 2026 · 23:06 UTCESCALATION #2 (148h active): Phishing - lucknight[.]comdomainabuse@tucows.com abuse@verisign-grs.com compliance@icann.org
-
Report #3 ICANN CC 535h still active Mar 3, 2026 · 01:57 UTCESCALATION #3 (535h active): Phishing - lucknight[.]comdomainabuse@tucows.com abuse@verisign-grs.com compliance@icann.org
-
Report #4 ICANN CC 571h still active Mar 4, 2026 · 14:24 UTCESCALATION #4 (571h active): Phishing - lucknight[.]comdomainabuse@tucows.com abuse@verisign-grs.com compliance@icann.org
-
Report #5 ICANN CC 616h still active Mar 6, 2026 · 10:52 UTCESCALATION #5 (616h active): Phishing - lucknight[.]comdomainabuse@tucows.com abuse@verisign-grs.com compliance@icann.org
-
Report #6 ICANN CC 1697h still active Apr 20, 2026 · 14:38 UTCESCALATION #6 (1697h active): Phishing - lucknight[.]comdomainabuse@tucows.com abuse@verisign-grs.com compliance@icann.org
-
Report #7 ICANN CC 2504h still active May 24, 2026 · 06:27 UTCESCALATION #7 (2504h active): Phishing - lucknight[.]comdomainabuse@tucows.com abuse@verisign-grs.com compliance@icann.org
VirusTotal 분석
보관된 증거
증거 및 외부 보고서
이 사이트로 인해 영향을 받으셨나요?
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
지역 당국에 신고하십시오
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
