跳转到安全报告
分析仪表盘
域安全和威胁情报
lloyds.reactivate-user.co 的网站图标

lloyds.reactivate-user.co

简要

lloyds.reactivate-user.co：冒充 Google，PhishDestroy 于 2026-09-15 检测到。风险：关键（100/100）。注册商：Dynadot。状态：内容不可用。托管：WIIT AG。PhishDestroy 已发送1 份滥用举报。VirusTotal：18/89 个引擎标记。已列入 Spamhaus DBL。请勿输入登录凭据，也不要连接钱包。

“Google”

Review the evidence
注册商
Dynadot
Resolved IP
89.163.155.33
Registered
2026年8月9日
PhishDestroy assessment 关键
可用性 内容不可用 最新观察中的内容不可用 观察到 · HTTP probe
风险信号
病毒检测总数：18/89 Spamhaus DBL: DBL_PHISH URLQuery threat systems: 4 alerts 自动品牌标签：Google
2026年9月15日 1 Report Sent
API
该域名已被标记为恶意域名
安全引擎报告检测：18。 请格外小心——不要输入凭据或个人信息。
VirusTotal
18 / 89
engine detections
URLQuery
4
threat alerts
页面快照
6
打开图库
域名年龄
76 days
已发送举报
1
查看时间线
报告概览

冒充 Google: lloyds.reactivate-user.co — 内容不可用. 证据摘要: VirusTotal 18/89 (alphaMountain.ai, BitDefender, CRDF, Ermes, ESET); URLQuery 4 alerts; Spamhaus…

为保留原始取证记录，下方的 PhishDestroy AI 详细分析仍使用英文。

来源证据VirusTotal 18 / 89 5 sources

VirusTotal

18 / 89 engine detections

打开报告

URLQuery

4 threat-system alerts

打开报告

Spamhaus DBL

DBL_PHISH

结果反映各来源的采集时间。零检出不代表安全。OTX 引用为社区发布的内容。

网络安全情报
Threat Detection Systems 4 alerts
Detection SystemIndicatorVerdictAlert
Quad9 DNS lloyds.reactivate-user.comaliciousSinkholed
Cloudflare DNS lloyds.reactivate-user.comaliciousSinkholed
DNS4EU lloyds.reactivate-user.comaliciousSinkholed
CIRA Canadian Shield DNS lloyds.reactivate-user.comaliciousSinkholed
Stored URLQuery scan evidence · Sep 15, 2026 14:18 UTC Open source report
CF Cloudflare Radar Verdict 恶意
Phishing
View full Cloudflare Radar report

Analysis

关键
VirusTotal
18 / 89
页面快照
6
页面快照 来源结果 注册记录

PhishDestroy threat report

Overview

lloyds.reactivate-user.co is an impersonation phishing site that uses the Lloyds name in its hostname, paired with a fake "reactivate user" pretext, to target Lloyds banking customers. PhishDestroy first detected it on 2026-09-15. The site has been offline since 2026-09-17, and on 2026-10-19 its DNS was still inactive. The page itself carried the title "Google", while we classified the site as impersonation phishing.

How the scam works

Schemes like this usually reach victims through a text or email claiming their account has been suspended or needs to be reactivated. The link leads to a lookalike login flow. Anything typed into it goes straight to the operators. That can include customer ID, password, memorable information, card details or one-time codes. With those details, criminals can take over online banking, add payees or talk victims into approving transfers.

Evidence

VirusTotal showed 18 of 89 engines flagging the domain on 2026-09-17, the same day it went offline. The vendors included BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, Emsisoft, alphaMountain.ai, CRDF and Ermes. That level of agreement from unrelated security vendors is strong for a short-lived phishing domain. Spamhaus listed it in its domain blocklist under the phishing category (DBL_PHISH), and it is on the PhishDestroy blocklist.

Infrastructure

The domain was registered through Dynadot Inc on 2026-08-09, about five weeks before we detected it. That gap fits a domain bought ahead of a campaign rather than one compromised by chance. It was hosted on a WIIT AG network in Germany. Its Let's Encrypt certificate gave it a browser padlock, but the padlock only means the connection was encrypted and says nothing about who ran the site.

What to do

If you entered any Lloyds login details on this site, contact Lloyds right away using the number on your card or in the official app, then change your password and memorable information. Review recent payments and new payees, and report any card or one-time code you shared so it can be cancelled. Treat any follow-up call claiming to be from the bank's fraud team with suspicion, and hang up and call back on the official number. Security teams should block the domain and the reactivate-user.co parent, and search mail and SMS logs for messages linking to it.

Useful links

urlscan.io scan and screenshotVirusTotal 报告Google Safe Browsing statusReport phishing to GoogleSite owner? Request a review

关于 lloyds.reactivate-user.co 的问题

lloyds.reactivate-user.co 是正规网站吗？

不是。PhishDestroy 将 lloyds.reactivate-user.co 归类为“冒充 Google”（风险：关键，100/100），首次检测于 2026-09-15。VirusTotal：18/89 个引擎标记。已列入 Spamhaus DBL。请将该网站视为不安全。

在 lloyds.reactivate-user.co 连接钱包安全吗？

不安全。请勿在 lloyds.reactivate-user.co 连接钱包、签署消息或批准代币。钓鱼网站会请求授权（approve、setApprovalForAll、Permit2），让运营者转走你的资产，而已确认的交易无法撤销。

如果我使用过 lloyds.reactivate-user.co，该怎么办？

更改你在该网站输入过的所有密码，并开启双重验证。如果你连接过钱包或签署过任何内容，请撤销授权，并将剩余资金转到新钱包；切勿透露助记词。分步指南：紧急处理指南。

延伸阅读

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list 查看来源

已保存的截图 · 6 张截图

主快照 1 / 6
来源主快照
Recorded2026-09-15 14:11 UTC
State已存档快照
Position1 / 6
打开快照 Wayback 下载

域名详情

域名
URLScan verdict 分析完成 score 0 report ↗
IP 信誉 abuse score 0/100 0 reports checked 2026年9月15日
注册商（主域名） Dynadot (Unknown)
滥用举报联系方式abuse@myloc.de, abuse@dynadot.com
ICANN 注册管理机构ICANN Lookup (RDAP) →
WHOIS查询reactivate-user.co 的 ICANN RDAP →
注册信息（主域名）reactivate-user.co · 创建 2026年8月9日 (76d · New) — Expires 2027年8月9日
首次不可用所需时间 44h
统计口径 从第一个存储的滥用报告到第一次观察到内容不可用所经过的时间。这并不能确定原因。
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据，例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情Provenance & timestamps
首次发现2026年9月15日
DOM Analysisanalyzed 2026年9月15日score 73/100
Submitted URLhttp://lloyds.reactivate-user.co/
Favicon Hash
案件 ID
Observed page title
Google
TLS 证书
颁发者 Let's Encrypt / YR1 · 存储的有效期将在 21 天后结束

网络 & 证书

已存档技术证据

网络 & DNS

Resolved IP
89.163.155.33
网络 ASN
AS24961
Organization
myLoc managed IT AG
Observed location
Frankfurt am Main, DE
Server header
gws

域名服务器 2

  • ns7.privatedns.vip
  • ns8.privatedns.vip

位置信息描述的是 IP 网络。

TLS 证书

Issuer
Let's Encrypt / YR1
生效时间
2026-08-17 15:09:43
到期时间
2026-11-15 15:09:42
Hostname coverage
证书主机名不匹配
Validity
在存档的有效期内
Collection time
2026-09-15 16:02:07 UTC
采集来源
PhishDestroy collector
证书指纹185cbb36534f68906ea66b1f8b3d268add5dddb206dd1d3d486dcfc0b9dcfae6
证书名称 · 1 个 SAN
  • www.lloyds.reactivate-user.co

已保存的证书元数据。未带时区的证书日期按存档原样显示。传输加密并不能证明该网站值得信任。

viewdns.info · 89.163.155.33rapiddns.io
Recorded subdomains1

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 record

The original observation time is not recorded for these hostnames.

技术 · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据，帮助保护他人

VirusTotal 分析

18 / 89 安全供应商标记了该域
在 VT 上查看
最近分析时间 上一份存档快照： 18 detections
alphaMountain.ai
BitDefender
CRDF
Ermes
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
Netcraft
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
网站性能分析

Google PageSpeed Insights — 移动端性能审核： lloyds.reactivate-user.co · checked Sep 15, 2026

83
Needs Work
Performance
FCP
2.47 s
首次内容绘制
LCP
2.63 s
Largest Contentful Paint
CLS
0.023
Cumulative Layout Shift
TBT
408 ms
Total Blocking Time
SI
2.8 s
Speed Index
数据来源： Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details1

Availability observations

最近一次可访问观测

估算时间描述的是一个观测时间窗口。它并不能证明注册商采取了措施，也不代表网站变为不可访问的确切时刻。

伪装检测

比较浏览器与爬虫各自收到的内容，并检查是否存在 Keitaro 流量分发。

lloyds.reactivate-user.co
已保存的结果
无法访问

已采集的来源详情

已存档的页面、网络和扫描器观测结果，按来源和观测时间分组。

Every stored field, with its source and date
URLScan · 2026-09-15T14:10:58Z

观察到: · Retrieved:

Uuid
01a0a568-002e-7000-86fe-ca7218b95992
Final url
https://www.google.com/
状态
200
已重定向
off-domain
Redirects
[
    {
        "to": "https://lloyds.reactivate-user.co/",
        "from": "http://lloyds.reactivate-user.co/",
        "status": 307
    },
    {
        "to": "https://google.com/",
        "from": "https://lloyds.reactivate-user.co/",
        "status": 302
    },
    {
        "to": "https://www.google.com/",
        "from": "https://google.com/",
        "status": 301
    }
]
Ip
142.251.150.119
Contacted domains
[
    "play.google.com",
    "ogads-pa.clients6.google.com",
    "www.gstatic.com",
    "google.com",
    "lloyds.reactivate-user.co"
]
Contacted IP addresses
[
    "2a00:1450:4001:c17::66",
    "142.251.14.95",
    "2a00:1450:4001:c15::5f",
    "142.251.150.119",
    "89.163.155.33"
]
Asns
[
    "15169",
    "24961"
]
Countries
[
    "DE",
    "US"
]
Linked domains
[
    "www.google.vu",
    "accounts.google.com",
    "search.app.goo.gl",
    "support.google.com",
    "policies.google.com",
    "about.google"
]
Document hash
63bd6e9b928609ac449e8f8f5929d037d0cb5858b951590e7fc0db2d358bbc35
Script hashes
[
    "e529858b564f2026b13f78424cef6a52f05ea1b73debe68671ea4b7962d37994",
    "83a1ae727f88b2fea87842524a25454e226dba29aee86c7b68ef6b6a50a0a244",
    "fd6d482936ba264abdd3cee9d923e824ca58310cc7db65f85dfc8b02df38db5c",
    "651eaef217ffde27fd0d447f0f2703176088ce3c7938db799521f233e912d6ea",
    "588f12638586fb0b2cf3ced74c64a1789b6d13f81b576abee26afeaed3aa49eb",
    "82a138b360cccd95bd5044e6bf3fb30b880f95519aa45fe75b3dd6677cfb7ec1",
    "93d2142b01ad05e3745ff947342712a160cd1f658c58c7291cbf89591f6c6c96"
]
Globals
[
    "_hst",
    "google",
    "jsac_init",
    "gws_wizbind",
    "gbar_",
    "_F_toggles_gbar_",
    "gbar",
    "__PVT",
    "U3bHHf",
    "__gr",
    "sbmlhf",
    "W_jd",
    "WIZ_global_data",
    "IJ_values",
    "_",
    "_DumpException",
    "_s",
    "_qs",
    "loaded_h_0",
    "_xjs_toggles",
    "_F_toggles",
    "_F_installCss",
    "jsl",
    "_F_jsUrl",
    "closure_uid_469352720",
    "closure_lm_723176",
    "_hm",
    "Aᶜstate",
    "closure_lm_506381",
    "silkcbr",
    "silk",
    "_F_installCssProto",
    "wiz_progress",
    "rwt",
    "chromeConnection",
    "userfeedback"
]
Cookies
[
    "PHPSESSID",
    "__Secure-STRP",
    "SEARCH_SAMESITE",
    "AEC",
    "NID",
    "__Secure-ENID"
]
Storage keys
[
    "__sak",
    "_c;;i",
    "hsb;;1789481451727",
    "hsb;;1789481451726",
    "udla::placeholder",
    "sb_wiz.zpc."
]
Tls
{
    "san": [
        "*.google.com",
        "*.appengine.google.com",
        "*.bdn.dev",
        "*.origin-test.bdn.dev",
        "*.cloud.google.com",
        "*.crowdsource.google.com",
        "*.datacompute.google.com",
        "*.google.ca",
        "*.google.cl",
        "*.google.co.in"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR2",
    "subject": "*.google.com",
    "protocol": "QUIC",
    "valid_to": "2026-11-02T08:37:34Z",
    "valid_from": "2026-08-10T08:37:35Z"
}
域名年龄（天）
4921
Apex age days
4921
Tls age days
36
TLS 有效天数
83
Umbrella rank
3
Requests
33
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -95,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "gws",
    "content-type": "text/html; charset=UTF-8",
    "x-frame-options": "SAMEORIGIN",
    "permissions-policy": "unload=()"
}
Cloudflare Radar · 2026-09-15T14:05:09Z

观察到: · Retrieved:

Uuid
dae5bf30-9b6c-4a75-93d7-9658e4223028
Final url
https://lloyds.reactivate-user.co/
状态
200
已重定向
same-domain
History
[
    {
        "url": "https://lloyds.reactivate-user.co/",
        "status": 302
    },
    {
        "url": "https://lloyds.reactivate-user.co/",
        "status": 200
    }
]
DOM structure hash
4fcba903bc4040be2d7f30e142801b421f95f2503972b2da38ae5f26c03a305c
Document hash
cac5b41ac3368f4a717c4514f569d23b53b82925e8639c86173166a5a50d086a
Phishing v2
[
    "phishing"
]
域名风险
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS 记录
[
    {
        "name": "lloyds.reactivate-user.co",
        "type": "A",
        "value": "89.163.155.33"
    }
]
DNSSEC 有效
false
Ip
89.163.155.33
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
VirusTotal · 2026-09-28T14:37:53Z

观察到: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 42,
    "malicious": 17,
    "suspicious": 1,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "ESET": "phishing",
    "Ermes": "not recommended",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Seclookup": "malicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
注册商
Dynadot Inc
创建
2026-08-09T10:52:52Z
Expires
2027-08-09T23:59:59Z
Updated
2026-08-14T10:57:02Z
首次发现
2026-08-16T14:32:04Z
DNS 记录
[
    {
        "ttl": 14400,
        "type": "TXT",
        "value": "v=spf1 +a +mx +ip4:93.186.197.131 ~all"
    },
    {
        "ttl": 14400,
        "type": "A",
        "value": "89.163.155.33"
    }
]
Dns at
2026-09-16T14:33:59Z
Jarm
29d29d15d29d29d00042d42d00000072e74222ce193a6f991becaa3da6c94d
Certificate
{
    "san": [
        "*.reactivate-user.co",
        "www.lloyds.reactivate-user.co"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "636d51bfebfd69337c18a2c13cad2a83ee5",
    "sha256": "185cbb36534f68906ea66b1f8b3d268add5dddb206dd1d3d486dcfc0b9dcfae6",
    "subject": "*.reactivate-user.co",
    "valid_to": "2026-11-15T15:09:42Z",
    "valid_from": "2026-08-17T15:09:43Z"
}
注册记录
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "https://www.dynadot.com/",
    "created": "2026-08-09T10:52:52Z",
    "updated": "2026-08-14T10:57:02Z",
    "expires": "2027-08-09T23:59:59Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns7.privatedns.vip",
        "ns8.privatedns.vip"
    ],
    "dnssec": "unsigned"
}
已存档的观测历史4

由监测程序和来源采集器保留的带日期变更记录。最新观测排在最前；来源状态并不能证明站点已被下架。

  1. 可用性监测 · 记录状态

    未知→dns_inactive

    dns_nxdomain

  2. 可用性监测 · 记录状态

    未知→dns_inactive

    dns_nxdomain

  3. 可用性监测 · 记录状态

    可访问→不可用

  4. VirusTotal · Detection count

    12→18

已记录的活动

4 entries
  1. VirusTotal

    18/89 engine detections

    查看来源
  2. 已发送滥用举报

    PD-20260915-8B933C

    abuse@myloc.de
  3. URLScan

    Page captured

    查看来源
  4. 已添加至 PhishDestroy

    lloyds.reactivate-user.co

    查看来源

证据与外部报告

证券分析
URLScan Analyzed VirusTotal 18 det. ChainPatrol URLQuery 4 threat alerts SSL 实验室 证书主机名不匹配 CF雷达 恶意 WOT ScamAdviser 黑名单检查器 URLVoid Sucuri SiteCheck MDN 观测站
已提交证据快照
Sent: 台账记录： 1 Case ID: PD-20260915-8B933C Recipient: abuse@myloc.de
随举报存档的页面标题： Lloyds Bank - Welcome to Online for Business
PDF notice generated Notice text archived (291 chars)
发送给服务商的滥用通知原文 
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
OSINT与情报分析
Web-Check Full scan SOCRadar 暗网报告 LeakIX Leak search Shodan Censys ThreatFox 哈德逊岩 登录凭据查询 IntelX crt.sh 证书 WHOIS Wayback
DNS 与网络
nslookup.io DNS bgp.tools ASN /路线
SEO 与域名
SpyFu Moz DA/PA Ahrefs 反向链接
深度分析
深度分析
Help & reporting

您是否受到本网站的影响？

5 个证据信号组已关联 1 条已存档通知记录 内容不可用
如果凭据已泄露，请立即报告。 切勿理会声称可追回资金的诈骗者。

如果您输入了帐户凭据、个人或付款信息，或者从此域下载了文件，请立即采取措施。以下资源可帮助您报告事件并保护自己。

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review 不是执法报告
域名申诉
如果您拥有该域名并认为该列表不正确，请请求审核
警惕“数据恢复”诈骗！ 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。

97个国家目录

Template-based draft · optional AI wording assistance requires separate consent

AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident

针对受害者的建议与指导

请根据您提供过的信息选择相应的步骤。请将本报告的副本与您自己的记录一并保存。

我应该立即采取什么措施？

紧急

停止使用可疑网站。请通过官方应用或您已信任的网址访问真正的服务。

  • 更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
  • 启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
  • 冻结卡片 如果您在钓鱼网站上输入了银行信息

我应该为报告收集哪些信息？

联邦调查局（FBI）指南

请将原始邮件、收据、消息和截图保存在安全的地方。基于事实的时间线有助于受理机构了解事件经过。 IC3 evidence guidance ↗

  • 付款记录 — 如果已付款，请保存收据、金额、日期、支付服务商和收款方信息。
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的（包括 lloyds.reactivate-user.co)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整，对调查仍有帮助。

我应该向哪里举报这起诈骗？
  • 联邦调查局（FBI）IC3 — 互联网犯罪投诉中心（美国联邦举报渠道）
  • 欧洲刑警组织 — 欧洲网络犯罪报告（欧盟）
  • Your bank or payment provider — 如果资金或银行卡信息已泄露，请通过官方联系方式尽快联系其反欺诈团队。
  • 当地警方 — 即使无法立即采取行动，也能留下正式记录

举报并不能保证追回损失或启动调查，但及时、准确的交易数据可以帮助执法机构和服务提供商追踪事件。

How do phishing scams typically work?
  • 虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
  • 退款诈骗 — 诈骗者冒充资金追回机构并索要预付费用。在独立核实服务方之前，切勿分享助记词或付款
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站，使得欺诈行为更难被察觉

将来我该如何保护自己？
  • 将官方网站添加到书签 — 切勿点击来自电子邮件、私信或广告中的链接
  • 验证域名 — 查看 PhishDestroy 在进行互动之前，请检查HTTPS、拼写和域名注册时间。
  • “好得令人难以置信”=骗局 — 保证收益、名人代言、紧迫的截止日期

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

检查任意域名

使用存储的阻止列表、WHOIS、DNS 和公共扫描证据进行威胁分析

立即扫描

举报网络钓鱼

将可疑域名提交至我们的威胁数据库——保护社区

报告

实时威胁动态

最近的网络钓鱼报告和观察到的可用性变化

监控

随时掌握最新信息，确保安全

请实时监控威胁，或者如果您认为这是误报，请对该条目提出异议

实时威胁动态 对该列表提出异议
关于本报告来源、观测日期与更正

本报告汇总了已保存的页面快照、注册与网络记录、扫描器结果以及 PhishDestroy 举报历史。每个来源均保留各自的观测日期。打开来源报告即可查看原始结果。

AI 辅助分析的撰写时间： 。该分析描述的是当时可获得的证据；之后的来源核查结果可能有所变化。

快照记录的是当时显示的内容。扫描器结果记录的是该服务商在检查时的评估。有效证书或零检出结果都不能保证安全。

Request a correction or appeal How PhishDestroy works
嵌入此报告附带证据链接的紧凑型小组件
HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html 
<iframe
  src="https://phishdestroy.io/zh/embed/domain/lloyds.reactivate-user.co"
  title="PhishDestroy threat report for lloyds.reactivate-user.co"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>