Security engines reporting a detection: 19. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
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.
RegistrationCreated Oct 16, 2026 (3d · Brand New!)—Expires Oct 16, 2027
Technical detailsProvenance & timestamps
First DetectedOct 19, 2026
Submitted URLhttp://frytt.dev/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
88.80.135.136
Nameservers 4
ns1bqx.name.com
ns2glx.name.com
ns3fqs.name.com
ns4ksy.name.com
TLS certificate
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 fingerprint71fa946bf5aa814625c4780924419386beb5442f3dcfa467163df4f54909566eCertificate 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.
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 evidence signal groups linked0 stored notification recordsUnverified
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
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.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including frytt.dev)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
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?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
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.
(SE)
