跳转到安全报告
域安全和威胁情报
frytt.dev favicon

frytt.dev

“Steam Community”

注册商
Name.com
Resolved IP
88.80.135.136
Registered
2026年10月16日
PhishDestroy assessment 关键
可用性 最后已知的活跃状态 最新存储的可达性观察 观察到 · HTTP probe
病毒检测总数:19/92 自动品牌标签:Counter-strike 年轻域名:3 天龄
2026年10月19日 1 Report Sent
API
该域名已被标记为恶意域名
安全引擎报告检测:19。 请格外小心——不要输入凭据或个人信息。
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Reports sent
view timeline
报告概览

冒充 Counter-strike: frytt.dev — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 19/92 (alphaMountain.ai, BitDefender, CRDF, CyRadar, Ermes); URLScan malicious verdict…

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

Source evidenceVirusTotal 19 / 92 6 sources

VirusTotal

19 / 92 engine detections

打开报告

Google Safe Browsing

No threat flag

打开报告

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

网络安全情报
CF Cloudflare Radar Verdict 恶意
Security Risks New Domains Security threats Phishing Phishing

Analysis

关键
VirusTotal
19 / 92
Page captures
2

PhishDestroy threat report

Overview

PhishDestroy has placed frytt.dev on its internal blocklist as a suspicious domain. The domain was first observed by PhishDestroy on 2026-10-19. No page title was recorded for the site. Google Safe Browsing checked the domain on 2026-10-19 and did not flag it. An external blocklist, OpenPhish, also listed the domain as of the same date.

How the scam works

The current evidence does not point to a specific malicious mechanism. Suspicious domains like this can be used for phishing, credential harvesting, or fraud, but no particular behavior has been observed on frytt.dev. Without a concrete classification, the risk remains undefined and should be treated with caution.

Evidence

VirusTotal retrieved on 2026-10-19 reported 19 detections out of 92 scanning engines, with vendors such as alphaMountain.ai, BitDefender, CRDF, CyRadar, Ermes, ESET, Emsisoft and Forcepoint ThreatSeeker flagging the site. Google Safe Browsing reported no threat on the same date. OpenPhish listed the domain, giving one external blocklist count. PhishDestroy’s internal list also includes frytt.dev. OTX showed zero pulses as of 2026-10-19.

Infrastructure

The domain was registered on 2026-10-16 through Name.com, Inc. The recorded IP address is 88.80.135.136. The domain was observed three days after registration. No further network or hosting details are available.

What to do

If you visited the site, avoid entering any credentials or personal information and monitor accounts for unexpected activity. Change passwords for any services where credentials may have been submitted. Security teams should add frytt.dev to blocklists, review access logs for connections to the recorded IP, and apply standard web‑filtering policies to this exact address.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

已保存的截图 · 2 captures

Observed page title
Steam Community
Automated brand references
Counter-strike Steam Valve
TLS 证书
颁发者 Let's Encrypt / YR1 · stored validity ends in 88 days

Domain details

域名
URLScan verdict 恶意 score 100 Phishing brand: Steam report ↗
IP 信誉 abuse score 0/100 0 reports checked 2026年10月20日
注册商 Name.com SE(SE)
滥用举报联系方式report@abuseradar.com, abuse@name.com
ICANN 注册管理机构ICANN Lookup (RDAP) →
注册信息创建 2026年10月16日 (3d · Brand New!) — Expires 2027年10月16日
HTTP 状态码200
技术详情Provenance & timestamps
首次发现2026年10月19日
DOM Analysisanalyzed 2026年10月20日score 98/1003 brand signals
Submitted URLhttp://frytt.dev/
Favicon Hash
案件 ID
ICANN OVERSIGHT

认证和 RAA 背景

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft 不会自动发送任何内容。

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
88.80.135.136
Network ASN
AS215362
Organization
zeroms.net
Observed location
Bucharest, RO
Server header
nginx

域名服务器 4

  • ns1bqx.name.com
  • ns2glx.name.com
  • ns3fqs.name.com
  • ns4ksy.name.com

Location describes the IP network.

TLS 证书

Issuer
Let's Encrypt / YR1
Valid from
2026-10-18 18:23:49
Valid until
2027-01-16 18:23:48
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-19 19:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint71fa946bf5aa814625c4780924419386beb5442f3dcfa467163df4f54909566e
Certificate names · 1 SANs
  • www.frytt.dev

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-19 23:03:01 UTC

Primary outcome 内容在线 reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation 内容在线 Ordinary HTTP content served 90% 2026-10-19 23:03:01 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-10-19 23:03:01 UTC last content: 2026-10-19 23:03:01 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.frytt.devDomain record

The original observation time is not recorded for these hostnames.

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

VirusTotal 分析

19 / 92 安全供应商标记了该域
View on VT
Last analyzed
alphaMountain.ai
BitDefender
CRDF
CyRadar
Ermes
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
Netcraft
OpenPhish
Seclookup
SOCRadar
Sophos
Webroot

存档证据

Wayback Machine Snapshot
历史快照可供证据审查
View Archive
网站性能分析

Google PageSpeed Insights — mobile performance audit of frytt.dev · checked Oct 19, 2026

56
Needs Work
Performance
FCP
6.15s
First Contentful Paint
LCP
7.73s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
10.95s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://frytt.dev/
Steam Community
响应
HTTP 200
HTML body
24.2 KB
Compressed
5.8 KB
Links
93 internal · 3 external
Detected technologies
jquerynginx
Selected response headers
Server: nginx
Content-Type: text/html; charset=utf-8
Cache-Control: no-cache
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 607ea6e6883404c7f835e4e270d4d46036c72fe0e7cfee4edc7323bf3f7b3319
Saved response-header values · 9
Cache-Control
no-cache
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Mon, 19 Oct 2026 18:30:51 GMT
Server
nginx
Transfer-Encoding
chunked
Vary
User-Agent
X-Revival-View
browser

Values retained by the collector; long values may be shortened during collection.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    未知→live_content

    content_served

  2. Availability monitor · First collection record

    可访问

Recorded activity

5 entries
  1. Abuse report sent

    PD-20261019-0D5110

    abuse@name.com
  2. URLScan

    Page captured

    View source
  3. Google Safe Browsing

    No threat flag

    View source
  4. VirusTotal

    19/92 engine detections

    View source
  5. Added to PhishDestroy

    frytt.dev

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

frytt.dev

证据与外部报告

已提交证据快照
Sent: Ledger records: 1 Case ID: PD-20261019-0D5110 Recipient: abuse@name.com
PDF notice generated
深度分析
Help & reporting

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

5 evidence signal groups linked 1 stored notification records 最后已知的活跃状态
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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

Official reporting routes

警惕“数据恢复”诈骗! 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

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

97个国家目录

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

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

针对受害者的建议与指导

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.

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

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

联邦调查局(FBI)指南

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的(包括 frytt.dev)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

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

我应该向哪里举报这起诈骗?

  • 联邦调查局(FBI)IC3 — 互联网犯罪投诉中心(美国联邦举报渠道)
  • 欧洲刑警组织 — 欧洲网络犯罪报告(欧盟)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 当地警方 — 即使无法立即采取行动,也能留下正式记录

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • 虚假网站 — 与正规网站完全一致的克隆网站,仅域名略有改动
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任,随后钱被骗走
  • 退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站,使得欺诈行为更难被察觉

将来我该如何保护自己?

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

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

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

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

实时威胁动态 对该列表提出异议
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

嵌入此报告

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

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