跳转到安全报告
分析仪表盘
⚠️
该域名已被标记为恶意域名
安全引擎报告检测：16。 报告匹配的公共黑名单：1。 请格外小心——不要输入凭据或个人信息。
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . A report was sent to the recorded registrar; contact details remain in Domain Intelligence. The latest stored availability evidence still shows the domain reachable; 4 months has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
4 months
Reports sent
1
Current status
Observed active at latest stored check
域安全和威胁情报

facebook-faq[.]se

“Facebook”

威胁判定 关键 95/100 证据评分
可用性 未验证 当前可达性未经验证
风险信号
病毒检测总数：16/91 存储的阻止列表匹配项：1 品牌冒充：Facebook
2026年4月15日 Facebook 1 Report Sent

证据摘要

重要
Evidence score
95/100

The domain facebook-faq.se has been identified as a brand impersonation threat specifically targeting Facebook users. Currently, the site has been taken offline, but its earlier presence posed a significant risk of credential theft. This domain was designed to mimic Facebook's login interface, tricking visitors into entering their username and password.

Technical analysis reveals that facebook-faq.se was flagged by 2 out of 95 security vendors on VirusTotal and appeared on 2 security blocklists. The domain resolved to IP address 81.170.159.187 and used an SSL certificate issued by Let's Encrypt with the R12 identifier, which is commonly abused by phishing sites to appear legitimate. The page title displayed was simply "Facebook," further indicating an attempt to deceive users.

Since the site is now offline, the immediate threat is reduced, but users who may have interacted with it should change their Facebook passwords immediately and enable two-factor authentication. PhishDestroy recommends always verifying URLs before logging in, especially when prompted by unsolicited links. For any suspicious activity, report the incident to Facebook's security team.

已提交证据快照

已发送
台账记录
1
案件 ID
PD-20260415-7B9D59
已捕获页面标题
Facebook
PDF 文件
PDF 证据
完整证据文本
Registrar: Loopia AB (Sweden (EU))
Policy Violations: “DNS Abuse Policy covers phishing, malware, botnets, pharming and deceptive websites; registrar may suspend, disable DNS or terminate domains to mitigate harm.”
Applicable Laws: Swedish Penal Code IT-related crimes; EU Directive 2013/40/EU
VirusTotal
VirusTotal
16 det.
URLQuery
URLQuery
2 det.
DNS Security
1/12
TLS 证书
Let's Encrypt
观测状态
未验证
PhishDestroy
DestroyList
已列入
Reports Sent
1

Data Coverage

VirusTotal 16 / 91 URLQuery 2 det. PhishStats checked — no match recorded OTX no community references CF雷达 scan completed URLScan capture 存储的报告 URLScan verdict 分析完成 DNS 阻断 1/12 TLS valid certificate, 64d WHOIS not parsed 屏幕截图 2 captures · 2 sources 重定向链 未探查
网络安全情报
DNS Provider Blocks 1 / 12
Brand Facebook
Suspicious · Checked 12 DNS providers: Quad9, AdGuard, ControlD, CleanBrowsing & more

威胁响应 Pipeline

发现
Checks
Reports
可用性
13/14

阻止列表覆盖

监控中的外部数据源 10 个 · 已存快照 2026年8月12日

PhishDestroy 源数据集 Phishunt 已列入
监控中的外部数据源 9 个 无匹配
MetaMask 无匹配 ScamSniffer 无匹配 Polkadot 无匹配 CryptoFirewall 无匹配 OpenPhish 无匹配 SEAL 无匹配 Enkrypt 无匹配 Codeesura 无匹配 DiscordPhishing 无匹配

已保存的截图

URLQuery capture 2 / 2
查看原图 来源报告 下载

域名情报

域名
URLScan Verdict 分析完成 score 0 report ↗
服务器 / ASN nginx · AS8473 Bahnhof AB
IP 信誉 IP abuse confidence 0/100 0 reports checked 2026年8月13日
注册商 未知
滥用举报联系方式abuse@bahnhof.net
IP 地址 81.170.159.187 SE
地理位置SE Borlänge, SE
网络AS8473 · Bahnhof AB
反向 IPviewdns.info → rapiddns.io →
Elapsed Since First Report 8 days
统计口径 Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 未验证.
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据，例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情DNS、TLS 名称和时间戳
首次发现2026年4月15日
Submitted URLhttp://facebook-faq.se/
域名服务器ns1.loopia.sens2.loopia.se
TLS 指纹
TLS 观测自 2026年3月21日 起有效扫描于 2026年4月15日
TLS 主体备用名称www.facebook-faq.se
页面标题
Facebook
TLS 证书
Valid transport encryption · 颁发者 Let's Encrypt · valid for 64 days
举报此域名 提交证据，帮助保护他人

VirusTotal 分析

16 / 91 安全供应商标记了该域
View on VT
Last analyzed Previous stored snapshot: 18 detections
ADMINUSLabs
Criminal IP
alphaMountain.ai
Certego
Chong Lua Dao
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
卡巴斯基
LevelBlue
Lionic
Seclookup
Sophos
VIPRE
网站性能分析

Google PageSpeed Insights — mobile performance audit of facebook-faq.se · checked Apr 15, 2026

96
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
2.01s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
195ms
Total Blocking Time
SI
1.98s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor

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

If credentials were compromised, report immediately. Do not engage with recovery scammers.

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

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

向当地主管部门报告

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

97个国家目录
AI辅助草稿——事件详细信息由AI提供商处理 自行审核并提交

检查任意域名

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

立即扫描

举报网络钓鱼

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

报告

实时威胁动态

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

监控

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

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

实时威胁动态 对该列表提出异议

外部工具

ScamAdviserScamAdviser 信任评分 100/100状态: Very Likely Safe打开来源
ChainPatrol URLQuery Google Safe Browsing SSL Labs Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
HTML · IFRAME

嵌入此报告

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

embed.html 
<iframe
  src="https://phishdestroy.io/zh/embed/domain/facebook-faq.se"
  title="PhishDestroy threat report for facebook-faq.se"
  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>