VirusTotal
18 / 89 engine detections
보고서 열기“Google”
lloyds.reactivate-user.co — 콘텐츠를 사용할 수 없음. 사기 유형: Impersonation. 증거 요약: VirusTotal 18/89 (alphaMountain.ai, BitDefender, CRDF, Ermes, ESET); URLQuery 4 alerts; Spamhaus DBL_PHISH; CF Radar malicious; PhishDestroy score 100/100. 등록기관: Dynadot.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
18 / 89 engine detections
보고서 열기4 threat-system alerts
보고서 열기악성
보고서 열기DBL_PHISH
no community references
보고서 열기No threat flag
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Quad9 DNS | lloyds.reactivate-user.co |
malicious | Sinkholed |
| Cloudflare DNS | lloyds.reactivate-user.co |
malicious | Sinkholed |
| DNS4EU | lloyds.reactivate-user.co |
malicious | Sinkholed |
| CIRA Canadian Shield DNS | lloyds.reactivate-user.co |
malicious | Sinkholed |
AI-assisted evidence review
On 2026-10-01, lloyds.reactivate-user.co returned an HTTP status code of 502 according to a recorded observation. The domain was first observed on 2026-09-15, and the same date carries a PageSpeed performance score of 83, so the earliest recorded observation is not limited to a single kind of measurement.
The HTTP check on 2026-10-01 recorded status 502, while the first observation of lloyds.reactivate-user.co dates to 2026-09-15. A PageSpeed check on 2026-09-15 returned a performance score of 83, and an SSL scan on the same date named the issuer as Let's Encrypt / YR1. VirusTotal, checked on 2026-09-17, reported 18 detections across 89 scanners, and the PhishDestroy internal listing was recorded as true. The IP address 89.163.155.33 is associated with the domain, located in DE and assigned to myLoc managed IT AG.
These records describe separate measurements taken by different sources on different dates, so they should be read as individual observations rather than a combined judgment. The VirusTotal detections and the PhishDestroy listing are distinct source records, and neither is interchangeable with the HTTP response or the PageSpeed score. The chronology from the first observation to the later checks shows the span over which records exist, but it does not by itself establish a change in the domain's behavior.
Preserve the HTTP response record for lloyds.reactivate-user.co alongside the PhishDestroy listing, since these are separate source records that can be compared later. Keep the VirusTotal detection record and the PageSpeed score as distinct items rather than merging them into one assessment. When reviewing the domain again, compare each preserved record against a fresh observation from the same source so that any difference reflects that source alone.
ns7.privatedns.vipns8.privatedns.vipLocation describes the IP network.
185cbb36534f68906ea66b1f8b3d268add5dddb206dd1d3d486dcfc0b9dcfae6www.lloyds.reactivate-user.coSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.lloyds.reactivate-user.coDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of lloyds.reactivate-user.co · checked Sep 15, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
lloyds.reactivate-user.co
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→dns_inactive
dns_nxdomain
접속 가능→이용 불가
12→18
No threat flag
View source18/89 engine detections
View sourcePD-20260915-8B933C
Page captured
View sourcelloyds.reactivate-user.co
View sourcePD-20260915-8B933C Recipient: abuse@myloc.de Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
lloyds.reactivate-user.co)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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.