Skip to security report
Analytics Dashboard
Domain security report
fun100x.network favicon

fun100x.network

Threat verdict
CriticalDomain Appeal
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
Risk signals
VirusTotal detections: 6/90 Scam type: Impersonation
Feb 26, 2026 CDN
API
Registrar
PDR
Resolved IP
104.21.20.199
Registered
Feb 21, 2026
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
This domain has been flagged as malicious
Security engines reporting a detection: 6. Exercise extreme caution — do not enter credentials or personal information.
Additional indicators at a glance
VirusTotal
VirusTotal
6 det.
URLScan
URLScan
Report ↗
TLS Certificate
Expired or unverified -170d
Age
8 mo
Observed status
Content unavailable
PhishDestroy
DestroyList
Listed

Source evidence

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

6 / 90

Report
Interpretation & limits

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

OTX

no community references

Report
Interpretation & limits

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

CF Radar

provider verdict: safe

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 capture

stored report

View stored capture ↗
Report
Interpretation & limits

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

URLScan verdict

Analysis completed

Report
Interpretation & limits

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

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.

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.

Evidence Summary

Critical
VirusTotal
6/90
URLScan
Stored capture

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

fun100x.network was registered on February 21, 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com. The domain resolves to the IP address 104.21.20.199, which belongs to Cloudflare, Inc. (AS13335) and is geolocated in the United States. Nameserver resolution points to earl.ns.cloudflare.com and melody.ns.cloudflare.com, confirming that the domain is fronted by Cloudflare’s edge network and is served over HTTP/3. The only HTTP response observed is a 403 status code, and the TLS handshake terminates with a certificate issued by Google Trust Services under the label WE1. The page title returned by the server is “Just a moment…”, which is a generic placeholder often used by Cloudflare challenge pages. No additional content was captured, so the exact phishing payload cannot be confirmed at this time. Threat intelligence flags the domain as a generic phishing site. It appears on a single security blocklist and has been explicitly blocked by PhishDestroy. Independent scoring systems show a Gridinsoft trust score of 0 out of 100, and VirusTotal reports a single security vendor flagging the domain. The combination of a newly created domain, use of Cloudflare protection, and a low trust score aligns with typical infrastructure choices observed in phishing campaigns. Because the underlying page content has not been disclosed, the specific brand or credential‑harvesting technique remains uncertain. However, the presence of a Cloudflare challenge page, a 403 response, and the “Just a moment…” title indicate an attempt to hide malicious redirects behind a short‑lived verification step. Defenders should continue to block the domain at perimeter filters, monitor DNS queries for the associated IP address, and incorporate the domain into threat‑intel feeds. Ongoing observation is recommended to capture any future payload changes.

Data coverage & collection18 · datasets with records / 13 · 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
6 / 90 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
Cloudflare Radar
safeCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
PDR Ltd. d/b/a PublicDomainRegistry.comCollection time not recorded
Network & DNS
104.21.20.199 · 1 · nameserversCollection time not recorded
TLS certificate
Google Trust Services / WE1
Page captures
2 · retained captures
Page analysis
0 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Availability history
14 · stored state changes
Source observation history
6 · stored source events
Community reports
Aggregate report counts and dates
IP reputation
Network-level observations
Not recorded in this report 13

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

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • PageSpeed performance
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.
Blocklist records0 · external source matches

Public Blocklist Status

Domain, network & archivePDR Ltd. d/b/a PublicDomainRegistry.com · 104.21.20.199 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar PDR IN(IN)
Abuse contactabuse@publicdomainregistry.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for fun100x.network →
RegistrationCreated Feb 21, 2026 (236d)
Cloaking Cloaking Detected Status split · score 4/6
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='fun100x.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
checked Oct 15, 2026
Time to First Unavailability 56 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 DetectedFeb 26, 2026
DOM Analysisanalyzed Apr 10, 2026score 78/100
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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.20.199
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • melody.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-01-29 08:44:46
Valid until
2026-04-29 09:43:26
Hostname coverage
Hostname coverage not recorded
Validity
Stored certificate expired
Collection time
2026-03-15 08:11:02 UTC
Collection source
PhishDestroy collector
Certificate fingerprint4563e7a0394ad387697f43df889a35209776b15b78be20b66642877302038b51

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

viewdns.info · 104.21.20.199rapiddns.io

Latest Classified Outcome 2026-10-14 20:21:26 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-15 01:13:04 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-13 22:27:48 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-13 22:27:48 UTC → 2026-09-30 16:14:55 UTC · 401.79h midpoint estimate ≈ 2026-09-22 07:21:21 UTC · precision 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 · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 90 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
Chong Lua Dao
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
401.79
Estimate basis
Bounded by observations
Estimate precision
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 checksStored browser and crawler observations
Detection-evasion evidence

Cloaking confirmed: scanners and visitors see different content

Observed Different content was served to scanners and to visitors

The page served one response to a browser-like visitor and another to a crawler or security scanner. Cloaking exists only to keep reviewers away from the real landing page.

Stored cloaking flag
Observed
Cloaking type
status_split
Cloaking score
4/6
Last cloaking scan

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

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Timeline & responseCollection 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. Domain Status Transition 2026-09-14 10:32:38 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  2. Domain Status Transition 2026-08-05 22:14:24 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from dead to alive.
  3. Domain Status Transition 2026-08-05 10:18:35 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  4. Cloudflare Radar Scan 2026-03-09 06:04:55 UTC
    Source: Cloudflare Radar
    Event details
    Cloudflare Radar scan registered: View Radar report.
  5. Cloudflare Radar Scan 2026-03-03 13:14:28 UTC
    Source: Cloudflare Radar
    Event details
    Cloudflare Radar scan registered: View Radar report.
  6. Domain Status Transition 2026-03-02 21:33:09 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
Stored observation history20

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

    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

Earlier observations 15
  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

    origin_unreachable · http_5xx

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  7. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  9. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  10. Availability monitor · Recorded state

    Reachable→Unavailable

  11. Availability monitor · Recorded state

    Unavailable→Reachable

  12. Availability monitor · Recorded state

    Reachable→Unavailable

  13. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/21ce18a9-7cc2-405e-97ab-6af5cddc13b2

  14. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/21ce18a9-7cc2-405e-97ab-6af5cddc13b2

  15. Availability monitor · Recorded state

    Reachable→Unavailable

Threat Response Pipeline

Discovery
Analysis
Monitoring

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

Threat Ingested
fun100x.network detected and queued for full analysis
Feb 26, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Mar 25, 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
6/90 recorded on VirusTotal
Sep 6, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Mar 25, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 15, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response; the cause was not independently established.
Sep 14, 2026
Site Came Back Online
Domain is responding again — monitoring resumed
Aug 6, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 200); the cause was not independently established.
Aug 5, 2026
Cloudflare Radar Scan
Scanned with Cloudflare Radar; network analysis completed.
Mar 9, 2026
Cloudflare Radar Scan
Scanned with Cloudflare Radar; network analysis completed.
Mar 3, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 403); the cause was not independently established.
Mar 2, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Feb 26, 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.
Jun 6, 2026
Time to First Unavailability
1339 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation
Related infrastructureShared hosting, registrar records and related domains
Community recordsRetained community reports and observations

Community reports

Reported by 1 community member, first seen Aug 6, 2025

Stored reports
1
Unique reported URLs
1
Accepted1
Evidence & investigation toolsOriginal reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 6 det. ChainPatrol URLQuery SSL Labs Hostname coverage not recorded CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reportingRecovery steps, reporting contacts and complaint drafts

Were You Affected by This Site?

3 evidence signal groups linked 0 reports recorded Content unavailable
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
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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
Embed this reportA 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/fun100x.network"
  title="PhishDestroy threat report for fun100x.network"
  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>