Skip to security report
Domain security report
ooteeqweiohgiudgyh.fly.dev favicon

ooteeqweiohgiudgyh.fly.dev

“Official Documents”

Threat verdict
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 20/94 URLQuery threat systems: 3 alerts Automated brand label: Adobe Google Safe Browsing: threat flag recorded
Mar 16, 2026 Adobe
API
Registrar
Fly.io
Resolved IP
66.241.125.129
Registered
Mar 16, 2026
2 sources
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 20. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

VirusTotal
VirusTotal
20 det.
URLQuery
URLQuery
3 threat alerts
CF Radar
Malicious
URLScan
URLScan
TLS Certificate
Expired or unverified dates -150d
E8 · Hostname coverage not recorded
Age
7 mo
Observed status
Content unavailable
PhishDestroy
DestroyList
Listed

Source evidence

9 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

20 / 94

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

3 threat-system alerts

Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

CF Radar

provider verdict: malicious

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan verdict

malicious

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

PhishStats

checked — no match recorded

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

no community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

stored report

Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence
Threat Detection Systems 3 alerts
Detection System Indicator Verdict Alert
CIRA Canadian Shield DNS ooteeqweiohgiudgyh.fly.dev malicious Sinkholed
DNS4EU ooteeqweiohgiudgyh.fly.dev malicious Sinkholed
Cloudflare DNS ooteeqweiohgiudgyh.fly.dev malicious Sinkholed
CF Cloudflare Radar Verdict Malicious
Security threats Phishing Phishing

Evidence Summary

Critical
VirusTotal
20/94
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

This domain, ooteeqweiohgiudgyh.fly.dev, is identified as a generic phishing site impersonating an official document page. The threat poses a high risk to users as it attempts to deceive them into providing sensitive information such as login credentials, personal data, or financial details. The domain's deceptive nature and association with official documents can lead to significant compromise of user data and potential financial loss.

Analysis indicates that 20 out of 95 security vendors on VirusTotal flag this domain as malicious. It is registered through Fly.io and resolves to the IP address 66.241.125.129, located in the United States and managed by AS40509 (Fly.io, Inc.). The domain appears on one security blocklist and is currently marked as offline. Google Safe Browsing also identifies the domain as a phishing site, further corroborating the high risk level.

If users have visited ooteeqweiohgiudgyh.fly.dev, they are advised to immediately change passwords for any accounts that may have been compromised. Additionally, users should monitor their financial statements and credit reports for any unauthorized activity. It is recommended to run a full system scan using updated antivirus software and to report the incident to their organization's IT security team. Users should also be cautious of similar domain names and verify the authenticity of any official document websites before providing sensitive information.

Data coverage & collection

21 · datasets with records / 10 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
20 / 94 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
3 · recorded detections / alerts
Google Safe Browsing
Threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
PhishStats
Dated lookup retained
Cloudflare Radar
maliciousCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Fly.ioCollection time not recorded
Network & DNS
66.241.125.129 · 0 · nameserversCollection time not recorded
TLS certificate
E8Collection time not recorded
Page captures
2 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
67/100 · mobile performance
Availability history
17 · stored state changes
Source observation history
1 · stored source events
Community reports
Aggregate report counts and dates
IP reputation
Network-level observations
Not recorded in this report 10

These checks have no retained result. This does not mean they passed or that a scan is running.

  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

Fly.io · 66.241.125.129 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Adobebrand: Genericemail report ↗
Google Safe Browsing Flagged Social engineering checked Mar 16, 2026
IP Reputation abuse score 0/100 0 reports checked Jul 14, 2026
Platform provider Fly.io
Abuse contactabuse@fly.io
Time to First Unavailability 3 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedMar 16, 2026
DOM Analysisanalyzed Jul 29, 2026score 88/1001 brand signal
Submitted URLhttp://ooteeqweiohgiudgyh.fly.dev/

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
66.241.125.129
Network ASN
AS40509
Organization
Fly.io, Inc.
Observed location
Pitkin, US
Server header
Fly/9e304e1bc (2026-03-11)

Location describes the IP network.

TLS certificate

Issuer
E8
Valid from
2026-02-21 23:24:17
Valid until
2026-05-21 23:24:17
Hostname coverage
Hostname coverage not recorded
Validity
Stored certificate expired
Collection source
PhishDestroy collector

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-17 08:21:17 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-17 01:08:26 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-03-23 22:17:55 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-03-23 22:17:55 UTC → 2026-09-30 16:14:55 UTC · 4,577.95h midpoint estimate ≈ 2026-06-27 07:16:25 UTC · precision very low · basis bounded
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.
Technologies · 11 identified
F
Fly.io
S
SweetAlert
Google Hosted Libraries
C
cdnjs
P
Popper
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

20 / 94 security vendors flagged this domain
View on VT
Last analyzed
ADMINUSLabs
Criminal IP
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safebrowsing
Gridinsoft
LevelBlue
Lionic
Netcraft
Sophos
URLQuery
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of ooteeqweiohgiudgyh.fly.dev · checked Mar 16, 2026

67
Needs Work
Performance
FCP
5.18s
First Contentful Paint
LCP
5.3s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
65ms
Total Blocking Time
SI
5.3s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
4577.95
Estimate basis
Bounded by observations
Estimate precision
very_low

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

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan

Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='ooteeqweiohgiudgyh.fly.dev', port=80): Max retries exceeded with url: / (Caused by NewConn

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
On demand

No live-check result has been retained.

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. VirusTotal Detections Update 2026-03-16 14:34:19 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 0 to 13. Added scanner alerts: ADMINUSLabs, BitDefender, CyRadar, ESET, Emsisoft, Fortinet, G-Data, Google Safebrowsing, LevelBlue, Netcraft, OpenPhish, Sophos, alphaMountain.ai.
Stored observation history18

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

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

Earlier observations 13
  1. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  8. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  9. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  10. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  11. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  12. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  13. VirusTotal · Detection count

    0→13

Threat Response Pipeline

Discovery
Analysis
Monitoring

14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
ooteeqweiohgiudgyh.fly.dev detected and queued for full analysis
Mar 16, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Mar 24, 2026
URLScan Verdict
URLScan returned a malicious verdict · score 100
Jul 29, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
20/94 recorded on VirusTotal
Mar 24, 2026
Google Safe Browsing
Mar 16, 2026
CF Radar: Malicious
Cloudflare Radar classified this domain as Security threats, phishing, Phishing
Brand Impersonation
Impersonation of Adobe
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Mar 24, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 18, 2026
VT Detection +13
+13 new detections (0 → 13): ADMINUSLabs, BitDefender, CyRadar, ESET +9
Mar 16, 2026
DestroyList Published
Mar 16, 2026
Content Observed Unavailable
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Mar 19, 2026
Time to First Unavailability
67 hours elapsed from detection to the first unavailable observation.
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

Related infrastructure

Shared hosting, registrar records and related domains

Community records

Retained community reports and observations

Community reports

Reported by 1 community member, first seen Mar 16, 2026

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & investigation tools

Original reports, independent checks and evidence links

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Content unavailable

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.

Official reporting routes
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 →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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 ooteeqweiohgiudgyh.fly.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)
  • Europol — European cybercrime reporting (EU)
  • 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

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

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: ooteeqweiohgiudgyh.fly.dev

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Official Documents”. Apparent target: Adobe.

VirusTotal detections for ooteeqweiohgiudgyh.fly.dev: 20 (2026-03-24 05:23:14 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

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