跳转到安全报告
⚠️
Suspicious Domain — Listed on PhishDestroy
存储的 PhishDestroy 威胁列表. VirusTotal analysis stored; no vendor detections were recorded at check time. 请格外小心——不要输入凭据或个人信息。
域安全和威胁情报

tinkerfcu[.]us[.]com

tinkerfcu.us.com 网络钓鱼与安全检查

“tinkerfcu.us.com | 502: Bad gateway”

威胁判定 已标记 63/100 证据评分
可用性 服务器错误 最新存储的响应不确定
风险信号
存储的 PhishDestroy 威胁列表
2026年6月15日 CDN
报告概览

tinkerfcu.us.com — 服务器错误 (HTTP 502). 证据摘要: VirusTotal 0/91; PhishDestroy score 63/100. 注册商: Instra.

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

证据摘要
FLAGGED
Ref
113BA1E2
评分
63/100

The domain tinkerfcu.us.com was registered on May 29, 2026 through Instra Corporation Pty Ltd. It resolves to the IP address 104.21.86.115, which belongs to a Cloudflare network located in Canada. The authoritative name servers are ns1‑ns4.centralnic.net. A Let's Encrypt certificate (E8) is active, indicating recent HTTPS provisioning.

Infrastructure analysis shows the site returns HTTP status code 502, suggesting a misconfigured or offline backend service. The domain is listed on a single security blocklist and has been actively blocked by PhishDestroy. Despite the presence on a blocklist, the Gridinsoft trust score is 0 out of 100, reinforcing the low reputation.

VirusTotal scans have reported 0 detections out of 95 engines, meaning the current payload or landing page has not yet been flagged by automated scanners. This lack of detection does not confirm benign intent; the classification as generic_phishing is based on observed behavior patterns and the blocklist entry.

Defenders should treat tinkerfcu.us.com as a potential phishing vector. Recommended actions include adding the domain to outbound web filters, monitoring DNS queries for the domain and its associated IP, and reviewing any user reports of credential‑harvesting attempts. Because the site is hosted behind Cloudflare, direct IP blocking may be ineffective, so domain‑level controls are advisable.

Uncertainty remains regarding the exact content served at the URL, as the 502 response prevents content retrieval. Continuous observation is required to detect any changes in HTTP response or new detections on threat intelligence platforms. The domain’s recent creation date and low trust score suggest it was likely deployed for a short‑term campaign.

VirusTotal
VirusTotal
0 det.
TLS 证书
Let's Encrypt / E8 3d
年龄
2 mo New
观测状态
服务器错误 502
PhishDestroy
DestroyList
已列入
数据覆盖范围 VirusTotal checked — no detections recorded URLQuery 未检查 PhishStats 未检查 OTX no community references CF雷达 no data URLScan capture not submitted URLScan verdict 无可用判定 DNS 阻断 未检查 TLS valid certificate, 3d WHOIS 2 mo old 屏幕截图 未捕获 重定向链 未探查

威胁响应 Pipeline

发现
Checks
Reports
可用性
5/7

公共封禁名单状态

域名情报

域名
服务器 / ASN cloudflare · AS13335 Cloudflare, Inc.
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
平台提供商 Instra
IP 地址 104.21.86.115 CDN
地理位置CA Toronto, CA
网络AS13335 · Cloudflare, Inc.
源 IP 隐藏在 CDN 代理后面。边缘地址的反向 IP 结果包含不相关的租户;查找源头需要被动 DNS 或证书透明数据。
HTTP 状态码502 Error
技术细节DNS、SSL SAN、时间戳
首次发现2026年6月15日
域名服务器ns4.centralnic.net
TLS Fingerprint
TLS Observationvalid from 2026年5月14日scanned 2026年6月19日
Favicon Hash
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

0 / 91 安全供应商标记了该域
View on VT
Last analyzed Previous stored snapshot: 0 detections
No VirusTotal engine marked the domain malicious in the stored analysis.

证据与外部报告

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

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

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

欧洲刑警组织
查找您所在欧盟国家/地区的官方报告渠道
National police directory
警惕“数据恢复”诈骗! 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

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

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

检查任意域名

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

立即扫描

举报网络钓鱼

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

报告

实时威胁动态

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

监控

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

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

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

嵌入此报告

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

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