Skip to security report
Domain security and threat intelligence
fgu.autos favicon

fgu.autos

“ReLai”

Threat verdict
Assessment sources

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

Availability Unverified Current reachability is unverified Observed · HTTP probe
VirusTotal detections: 5/89
OTX: 4 refs Sep 4, 2026
API
Registrar
Dynadot
Resolved IP
38.47.238.196
Registered
Jul 23, 2026
Stored Capture

No stored capture is available for this domain.

This domain has been flagged as malicious
Security engines reporting a detection: 5. Exercise extreme caution — do not enter credentials or personal information.
Additional indicators at a glance
VirusTotal
VirusTotal
5 det.
OTX references
ScamAdviser
Scamadviser
80/100Likely Safe
TLS Certificate
Expired or unverified
Age
3 mo New
PhishDestroy
DestroyList
Listed

Source evidence

5 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

5 / 89

Report
Interpretation & limits

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

OTX

4 community references

Report
Interpretation & limits

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

CF Radar

provider verdict: clean

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.

Scamadviser

80/100

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.

Google Safe Browsing

Checked; no 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.

Evidence Summary

Critical
VirusTotal
5/89
OTX
4 community refs

Stored narrative · generated . Provider checks below retain their own observation dates.

Assessment

fgu.autos returned HTTP status 200 in an HTTP check recorded on 2026-10-01, the most recent availability observation in this evidence set. The same domain was first observed on 2026-09-04, roughly four weeks earlier, according to the recorded first-observation date.

Recorded Evidence

The HTTP check on 2026-10-01 recorded status 200 for fgu.autos, while the first observation of the domain is dated 2026-09-04. VirusTotal, checked on 2026-09-18, reported 5 detections across 89 scanners, and OTX, checked on 2026-09-14, listed 4 pulses. The PhishDestroy internal listing was recorded as true, and a PageSpeed check on 2026-09-14 produced a performance score of 96. The registrar is Dynadot Inc, and the SSL certificate issuer is Let's Encrypt / YR1, scanned on 2026-09-14.

Interpretation

The HTTP 200 record describes only the response captured on that date, not the domain's content or its present availability. The VirusTotal and OTX figures reflect separate source observations made on different dates, so they should be read as distinct records rather than combined into a single trend. The PhishDestroy listing and the PageSpeed score likewise come from different checks, and the chronology from first observation to the HTTP check spans several weeks without establishing what occurred in between.

Recommended Actions

Preserve the fgu.autos HTTP check record and the PhishDestroy listing entry as separate source records for later comparison. Compare the VirusTotal and OTX observations against future checks of fgu.autos, keeping each source's own record distinct. Retain the PageSpeed result alongside these records so that later measurements of fgu.autos can be reviewed against the same source set.

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='fgu.autos', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOCK

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting

Domain details

Domain
IP Reputation abuse score 1/100 1 report PhishingBad Web Bot checked Oct 14, 2026
OTX Tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
Abuse contact["abuse@dynadot.com"]
RegistrationCreated Jul 23, 2026 (83d · New) — Expires Jul 23, 2027
Technical detailsProvenance & timestamps
First DetectedSep 4, 2026
Favicon Hash
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
38.47.238.196
Network ASN
AS140227
Organization
Hong Kong Communications International Co., Limited
Observed location
Los Angeles, US
Server header
nginx

Nameservers 1

  • ns2.dyna-ns.net

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-08-26 12:22:05
Valid until
2026-11-24 12:22:04
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-14 19:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintbbb552bbd63227b525903a60e5b9da3ecc2340f93992d73e1c12c5bd6858ac6f
Certificate names · 14 SANs
  • bcf.autos
  • bfe.lat
  • esd.autos
  • fcv.autos
  • gdb.autos
  • ghu.autos
  • hdu.lat
  • hfs.lat
  • jfm.lat
  • jfu.lat
  • jgc.lat
  • kfh.autos
  • mhx.lat
  • whu.autos

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

viewdns.info · 38.47.238.196rapiddns.io

Latest Classified Outcome 2026-10-14 10:18:46 UTC

Primary outcome Live content 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 Live content Ordinary HTTP content served 90% 2026-10-14 10:18:46 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-14 10:18:46 UTC last content: 2026-10-14 10:18:46 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.
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
SOCRadar
VIPRE
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of fgu.autos · checked Sep 14, 2026

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

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. Threat First Observed 2026-09-14 16:53:11 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive.

Threat Response Pipeline

Discovery
Analysis
Monitoring

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

Threat Ingested
fgu.autos detected and queued for full analysis
Sep 4, 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
5/89 recorded on VirusTotal
Sep 18, 2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 15, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 15, 2026
DestroyList Published
Sep 4, 2026
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.

Community intelligence

1 community report

CategoryPIGBUTCHERING

I was contacted via telegram by someone claiming to work for a company that increased app views. When you viewed an app- you were paid 5-10$ per app. Then you had to complete a “node tasks “ with bitcoin in order to become a full time employee and receive your commissions. Upon c

Evidence & External Reports

Community Scam Report — ChainAbuse
1 report filed for fgu.autos (1 written by a person) · category: Pigbutchering · source checked
“I was contacted via telegram by someone claiming to work for a company that increased app views. When you viewed an app- you were paid 5-10$ per app. Then you had to complete a “node tasks “ with bitcoin in order to become a full time employee and receive your commissions. Upon completing task 1 I sent $240 in bitcoin then was told I had to complete task 2 to cash out my original payment and that would cost $700 when I did that they said their financial department was closing and I had to wait u”
— reported by Anonymous on Sep 4, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
Deep Analysis

Were You Affected by This Site?

3 evidence signal groups linked 0 reports recorded Unverified
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.

Europol
Find the official reporting channel for your EU country
National police directory
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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

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