Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 17/92 engines flagged. malicious: 15. suspicious: 2. Analysis time (as stored): 2026-10-29T23:22:25Z. Retrieved (as stored): 2026-11-08T02:01:07Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
entry5300-js2024r1.usercontent.dev favicon

entry5300-js2024r1.usercontent.dev

In short

On 2026-07-01, entry5300-js2024r1.usercontent.dev displayed a page titled "Log in to Telegram by QR Code." The page shows a QR code with a Telegram logo at its center, followed by three numbered steps instructing the user to open Telegram on their phone, navigate to Settings > Devices > Link Desktop Device, and point the phone at the screen to confirm login. Below the steps, two links offer login by phone number and continuing in Dutch.

“Telegram Web”

Review the evidence
Registrar
United StatesGoDaddy
Resolved IP
Netherlands178.128.255.27DigitalOcean, LLC
Registered
Apr 15, 2019
First observed
Nov 7, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 17/92 Google Safe Browsing: threat flag recorded
VirusTotal
17 / 92
engine detections ·
Google Safe Browsing
Flagged
URLScan
Malicious
Cloudflare Radar
Phishing
Page captures
3
open gallery
Domain age
2,764 days
registered 2019-04-15 according to WHOIS · source data differ
Nov 7, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded entry5300-js2024r1.usercontent.dev on 2026-11-07. Stored VirusTotal result: 17/92 engines flagged. malicious: 15. suspicious: 2. Analysis time (as stored): 2026-10-29T23:22:25Z. Retrieved (as stored): 2026-11-08T02:01:07Z. Google Safe Browsing flags it. Risk: critical (100/100). Registrar: GoDaddy. Status: Last known active. Hosting: DigitalOcean, LLC. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
17 / 92
Hosting
Netherlands178.128.255.27DigitalOcean, LLC
Registrar
United StatesGoDaddy
Registered
Apr 15, 2019
Page captures
3
Page captures Source results Registration record

Capture recorded with this analysis · URLScan · 2026-07-01T18:43:08Z
SHA-256: 17cdc6a2817af5037b9bc41defdb7ea0e93e326c0ce70d82881f53c030349f36

PhishDestroy analysis, reviewed version

On 2026-07-01, entry5300-js2024r1.usercontent.dev displayed a page titled "Log in to Telegram by QR Code." The page shows a QR code with a Telegram logo at its center, followed by three numbered steps instructing the user to open Telegram on their phone, navigate to Settings > Devices > Link Desktop Device, and point the phone at the screen to confirm login. Below the steps, two links offer login by phone number and continuing in Dutch.

The stored VirusTotal domain result reports 17 detections out of 92 engines. CRDF reported "malicious"; ESET reported "phishing".

Source evidenceVirusTotal 17 / 92 · Google Safe Browsing: flagged 8 sources

VirusTotal

17 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
45
Malicious
15
Suspicious
2
Undetected
30

Vendor labels

CRDF
malicious
ESET
phishing
VIPRE
malware
Lionic
phishing
Sophos
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
spam
Netcraft
malicious
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
Criminal IP
phishing
Yandex Safebrowsing
phishing
Google Safe Browsing
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

Sophos
phishing and fraud
Webroot
Phishing and Other Frauds
Forcepoint ThreatSeeker
phishing and other frauds

Created

Updated

First seen

DNS records

  • TTL, seconds
    600
    Type
    A
    Value
    178.128.255.27

DNS records observed

JARM fingerprint

29d29d15d29d29d21c29d29d29d29d74aaecca9f9c4a3303863dfee62b241e

Certificate

Subject alternative names
  • *.usercontent.dev
  • usercontent.dev
Issuer
GoDaddy.com / GoDaddy TLS Intermediate CA DV - R1v1
Serial
57492fd398846582
SHA-256
666b1d783ec22978927e965dc357339f5e59ad2eec4466acefa9a85df8d0e5b8
Subject
*.usercontent.dev
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 15,
    "suspicious": 2,
    "undetected": 30
}
Vendor labels
{
    "CRDF": "malicious",
    "ESET": "phishing",
    "VIPRE": "malware",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "spam",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "Criminal IP": "phishing",
    "Yandex Safebrowsing": "phishing",
    "Google Safe Browsing": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Created
2019-04-15T00:00:00Z
Updated
2026-04-15T00:00:00Z
First seen
2024-05-07T10:30:45Z
DNS records
[
    {
        "ttl": 600,
        "type": "A",
        "value": "178.128.255.27"
    }
]
Dns at
2026-10-29T23:22:42Z
Jarm
29d29d15d29d29d21c29d29d29d29d74aaecca9f9c4a3303863dfee62b241e
Certificate
{
    "san": [
        "*.usercontent.dev",
        "usercontent.dev"
    ],
    "issuer": "GoDaddy.com / GoDaddy TLS Intermediate CA DV - R1v1",
    "serial": "57492fd398846582",
    "sha256": "666b1d783ec22978927e965dc357339f5e59ad2eec4466acefa9a85df8d0e5b8",
    "subject": "*.usercontent.dev",
    "valid_to": "2027-04-06T11:32:44Z",
    "valid_from": "2026-09-20T11:32:44Z"
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
17
denominator
92
malicious
null
suspicious
null
vendors
["Criminal IP","CRDF","ESET","Emsisoft","Forcepoint ThreatSeeker","Fortinet","Google Safe Browsing","Gridinsoft","Kaspersky","Lionic","Netcraft","Seclookup","SOCRadar","Sophos","VIPRE","Webroot","Yandex Safebrowsing"]
observed_at
2026-10-29 23:22:25
checked_at
2026-11-08 03:01:08
fetched_at
2026-11-08 02:01:08
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Report ID

8061f119-cad5-4d68-b249-aa6c49382652

Final URL

https://entry5300-js2024r1.usercontent.dev/

HTTP response

200

Navigation history

  • URL
    https://entry5300-js2024r1.usercontent.dev/
    Status
    200

DOM structure hash

deab21b4a7872216ebe986a67c9987db07f7888c56591decc8d8fab3d36cafd2

Document hash

a50e53873a9fcb4dea985ea0b1a32825f15fa53f5e68ae76ca428289d4b1c199

Phishing classifier result

  • phishing

URL risk categories

  • Phishing

Domain risk categories

  • Malware
  • Security threats
  • Phishing
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    entry5300-js2024r1.usercontent.dev
    Type
    A
    Value
    178.128.255.27

DNSSEC valid

No

IP address

127.0.1.20

127.0.1.20 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
GoDaddy.com, LLC
Registered
Updated
Expires
Nameservers
  • pdns11.domaincontrol.com
  • pdns12.domaincontrol.com
Original source fields · JSON
Uuid
8061f119-cad5-4d68-b249-aa6c49382652
Final url
https://entry5300-js2024r1.usercontent.dev/
Status
200
History
[
    {
        "url": "https://entry5300-js2024r1.usercontent.dev/",
        "status": 200
    }
]
DOM structure hash
deab21b4a7872216ebe986a67c9987db07f7888c56591decc8d8fab3d36cafd2
Document hash
a50e53873a9fcb4dea985ea0b1a32825f15fa53f5e68ae76ca428289d4b1c199
Phishing v2
[
    "phishing"
]
Url risks
[
    "Phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "Phishing",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "entry5300-js2024r1.usercontent.dev",
        "type": "A",
        "value": "178.128.255.27"
    }
]
Dnssec valid
false
Ip
127.0.1.20

127.0.1.20 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "created": "2019-04-15T12:51:40Z",
    "updated": "2026-05-30T12:51:40Z",
    "expires": "2027-04-15T12:51:40Z",
    "nameservers": [
        "pdns11.domaincontrol.com",
        "pdns12.domaincontrol.com"
    ]
}
Separate stored summary: Not recorded · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
null
categories
[]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Malicious

SHA-256 226399d71eae4d5b60b2854209d6f4d49a42c557bde6a811c0e0ce21a0a23a47

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

019f1efd-e0cb-7318-8a86-22fb69ba7159

Final URL

https://entry5300-js2024r1.usercontent.dev/

HTTP response

200

IP address

178.128.255.27

Contacted IP addresses

  • 178.128.255.27

Autonomous systems (ASN)

  • 14061

Server countries

  • NL

Document hash

a50e53873a9fcb4dea985ea0b1a32825f15fa53f5e68ae76ca428289d4b1c199

Script hashes

  • fcf2bb1c2eec25966834a9649bba8f29cdd0a519888108ec33547be0e52c24f3
  • 2f92606f2c333618321af99c063a8cf736bce47536c89b5b7cbd05ccbb0c1dbe
  • 900f22723c45f67600638812021437a089daa7c2f0a559ebb85a0726183cee79
  • 8528a55ba5d25bb2b6463f369b7a2046c08ced5f20256978a06119c0d50d08a2
  • 9eeddd1d2a24596fab4825030e466b0702d368e1b987980e6329151af2a6bf34
  • 49df7ed82b2bdd3fbd949ee8a07181cf982f6c6e1667f635429cb3fcd9bbccc4
  • c3195442e9136cf3ff7799a59e52daadd15fb900511ea38faae151194ba7ab79
  • 114c7f7999db3bdfb48c96e8b7f3af28153cf75027cd2ca363b4e354588cf5a3
  • 36cb02e59322028c02c5365bd56cbd129b3eb2fb4aaec625160ca2dc9786a4bd
  • 6c4900d40f3335423817340edddd7655d96e707156923fcf3cbf5a6520008d6e

JavaScript globals

  • rootScope
  • deferredPromise
  • AppStorage
  • stateStorage
  • wrapUrl
  • I18n
  • webpWorkerController
  • appStorage
  • singleInstance
  • webPushApiManager
  • telegramMeWebManager
  • opusDecodeController
  • cryptoMessagePort
  • mtprotoMessagePort
  • serviceMessagePort
  • apiManagerProxy
  • calcImageInBox
  • mediaSizes
  • customProperties
  • windowSize
  • liteMode
  • themeController
  • overlayCounter
  • formatDateAccordingToTodayNew
  • fillTipDates
  • dispatchHeavyAnimationEvent
  • pagesManager
  • sequentialDom
  • putPreloader

Browser storage keys

  • xt_instance
  • state_id
  • k_build
  • dc
  • server_time_offset
  • auth_key_fingerprint
  • dc2_auth_key
  • dc2_server_salt

TLS session and certificate

Subject alternative names
  • *.usercontent.dev
  • usercontent.dev
Cipher
AES_128_GCM
Issuer
Go Daddy Secure Certificate Authority - G2
Subject
*.usercontent.dev
Protocol
TLS 1.2
Valid until
Valid from

Domain age, days

785

Differs from the registration date in WHOIS (2019-04-15), which gives 2634 days on the scan date 2026-07-01. The two sources disagree; both values are kept as recorded.

Registered domain age, days

2413

Differs from the registration date in WHOIS (2019-04-15), which gives 2634 days on the scan date 2026-07-01. The two sources disagree; both values are kept as recorded.

Certificate age, days

285

Certificate validity, days

397

Page requests

23

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
93
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • telegram
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Telegram
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
nginx/1.10.3
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
019f1efd-e0cb-7318-8a86-22fb69ba7159
Final url
https://entry5300-js2024r1.usercontent.dev/
Status
200
Ip
178.128.255.27
Contacted IP addresses
[
    "178.128.255.27"
]
Asns
[
    "14061"
]
Countries
[
    "NL"
]
Document hash
a50e53873a9fcb4dea985ea0b1a32825f15fa53f5e68ae76ca428289d4b1c199
Script hashes
[
    "fcf2bb1c2eec25966834a9649bba8f29cdd0a519888108ec33547be0e52c24f3",
    "2f92606f2c333618321af99c063a8cf736bce47536c89b5b7cbd05ccbb0c1dbe",
    "900f22723c45f67600638812021437a089daa7c2f0a559ebb85a0726183cee79",
    "8528a55ba5d25bb2b6463f369b7a2046c08ced5f20256978a06119c0d50d08a2",
    "9eeddd1d2a24596fab4825030e466b0702d368e1b987980e6329151af2a6bf34",
    "49df7ed82b2bdd3fbd949ee8a07181cf982f6c6e1667f635429cb3fcd9bbccc4",
    "c3195442e9136cf3ff7799a59e52daadd15fb900511ea38faae151194ba7ab79",
    "114c7f7999db3bdfb48c96e8b7f3af28153cf75027cd2ca363b4e354588cf5a3",
    "36cb02e59322028c02c5365bd56cbd129b3eb2fb4aaec625160ca2dc9786a4bd",
    "6c4900d40f3335423817340edddd7655d96e707156923fcf3cbf5a6520008d6e"
]
Globals
[
    "rootScope",
    "deferredPromise",
    "AppStorage",
    "stateStorage",
    "wrapUrl",
    "I18n",
    "webpWorkerController",
    "appStorage",
    "singleInstance",
    "webPushApiManager",
    "telegramMeWebManager",
    "opusDecodeController",
    "cryptoMessagePort",
    "mtprotoMessagePort",
    "serviceMessagePort",
    "apiManagerProxy",
    "calcImageInBox",
    "mediaSizes",
    "customProperties",
    "windowSize",
    "liteMode",
    "themeController",
    "overlayCounter",
    "formatDateAccordingToTodayNew",
    "fillTipDates",
    "dispatchHeavyAnimationEvent",
    "pagesManager",
    "sequentialDom",
    "putPreloader"
]
Storage keys
[
    "xt_instance",
    "state_id",
    "k_build",
    "dc",
    "server_time_offset",
    "auth_key_fingerprint",
    "dc2_auth_key",
    "dc2_server_salt"
]
Tls
{
    "san": [
        "*.usercontent.dev",
        "usercontent.dev"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "Go Daddy Secure Certificate Authority - G2",
    "subject": "*.usercontent.dev",
    "protocol": "TLS 1.2",
    "valid_to": "2026-10-21T11:27:19Z",
    "valid_from": "2025-09-19T11:27:19Z"
}
Domain age days
785

Differs from the registration date in WHOIS (2019-04-15), which gives 2634 days on the scan date 2026-07-01. The two sources disagree; both values are kept as recorded.

Apex age days
2413

Differs from the registration date in WHOIS (2019-04-15), which gives 2634 days on the scan date 2026-07-01. The two sources disagree; both values are kept as recorded.

Tls age days
285
Tls valid days
397
Requests
23
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 93,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "telegram"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Telegram"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "nginx/1.10.3",
    "content-type": "text/html; charset=UTF-8"
}

OTX

no community references

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
entry5300-js2024r1.usercontent.dev: Telegram QR Code Login Page
ai_description
PhishDestroy records entry5300-js2024r1.usercontent.dev as a page displaying a Telegram QR code login screen with phone number and Dutch language options.
ai_summary
On 2026-07-01, entry5300-js2024r1.usercontent.dev displayed a page titled "Log in to Telegram by QR Code." The page shows a QR code with a Telegram logo at its center, followed by three numbered steps instructing the user to open Telegram on their phone, navigate to Settings > Devices > Link Desktop Device, and point the phone at the screen to confirm login. Below the steps, two links offer login by phone number and continuing in Dutch. The stored VirusTotal domain result reports 17 detections out of 92 engines. CRDF reported "malicious"; ESET reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-08 03:06:26
revision
745e9425e2eb3ead63020390cb7acc02b4fd4be2e74e92c60027e784551fae93
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 21 fields

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
2
Snapshots per day
0
Average page size, bytes
5783

Page title and metadata

Open Graph URL
https://web.telegram.org/k/
Page title
Telegram Web
Open Graph type
website
Open Graph image
assets/img/android-chrome-192x192.png?v=jw3mK7G9Ry
Open Graph title
Telegram Web
Theme color
#ffffff
Description
Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed.
Canonical URL
https://web.telegram.org/
Open Graph description
Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed.

Trackers

Requests
19

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
71
TLS
56
Waiting
14
Connection
14
Download
0
Response time, ms
155

TLS connection

ALPN
http/1.1
Cipher
ECDHE-RSA-AES128-GCM-SHA256
Protocol
TLSv1.2
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
Certificate authorized
Yes
OCSP stapling
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
13603
CO₂, grams
0.0005
Cleaner than, %
65

DNS servers

Nameservers
  • IP address
    97.74.111.55
    Host
    pdns11.domaincontrol.com
  • IP address
    173.201.79.55
    Host
    pdns12.domaincontrol.com
DNS zone
usercontent.dev

Location

IP address
178.128.255.27
ASN
14061
Organization
DigitalOcean, LLC
City
Amsterdam
Country
NL

TLS certificate

Issuer
GoDaddy.com / GoDaddy TLS Intermediate CA DV - R1v1
Subject
*.usercontent.dev

DNS records

A
  • 178.128.255.27

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
178.128.255.27
IP version
4

Redirects

Redirect chain
  • https://entry5300-js2024r1.usercontent.dev

Subdomains

Count
2
Subdomains
  • jschart.usercontent.dev
  • www.jschart.usercontent.dev

Technology stack

Technologies
  • Nginx
  • HSTS
  • PWA
  • Open Graph

HTTP headers

Response headers
Server
nginx/1.10.3
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2025-04-23T00:55:14Z",
    "first": "2024-08-11T01:39:02Z",
    "changes": 0,
    "days_archived": 2,
    "scans_per_day": 0,
    "avg_page_bytes": 5783
}
Page title and metadata
{
    "ogUrl": "https://web.telegram.org/k/",
    "title": "Telegram Web",
    "ogType": "website",
    "ogImage": "assets/img/android-chrome-192x192.png?v=jw3mK7G9Ry",
    "ogTitle": "Telegram Web",
    "themeColor": "#ffffff",
    "description": "Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed.",
    "canonicalUrl": "https://web.telegram.org/",
    "ogDescription": "Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed."
}
Trackers
{
    "requests": 19
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 71,
        "tls": 56,
        "wait": 14,
        "connect": 14,
        "download": 0
    },
    "response_ms": 155
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "ECDHE-RSA-AES128-GCM-SHA256",
    "protocol": "TLSv1.2",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2"
    ],
    "authorized": true,
    "ocsp_stapled": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 13603,
    "co2_grams": 0.0005,
    "cleaner_than": 65
}
Dns server
{
    "ns": [
        {
            "ip": "97.74.111.55",
            "host": "pdns11.domaincontrol.com"
        },
        {
            "ip": "173.201.79.55",
            "host": "pdns12.domaincontrol.com"
        }
    ],
    "zone": "usercontent.dev"
}
Location
{
    "ip": "178.128.255.27",
    "asn": "14061",
    "org": "DigitalOcean, LLC",
    "city": "Amsterdam",
    "country": "NL"
}
Ssl
{
    "issuer": "GoDaddy.com / GoDaddy TLS Intermediate CA DV - R1v1",
    "subject": "*.usercontent.dev"
}
DNS records
{
    "A": [
        "178.128.255.27"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "178.128.255.27",
    "family": 4
}
Redirects
{
    "chain": [
        "https://entry5300-js2024r1.usercontent.dev"
    ]
}
Subdomains
{
    "count": 2,
    "subdomains": [
        "jschart.usercontent.dev",
        "www.jschart.usercontent.dev"
    ]
}
Tech stack
{
    "technologies": [
        "Nginx",
        "HSTS",
        "PWA",
        "Open Graph"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx/1.10.3",
        "content-type": "text/html; charset=UTF-8"
    }
}

Questions about entry5300-js2024r1.usercontent.dev

Is entry5300-js2024r1.usercontent.dev legit?

PhishDestroy rates entry5300-js2024r1.usercontent.dev as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-07. Stored VirusTotal result: 17/92 engines flagged. malicious: 15. suspicious: 2. Analysis time (as stored): 2026-10-29T23:22:25Z. Retrieved (as stored): 2026-11-08T02:01:07Z. Google Safe Browsing flags it. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is entry5300-js2024r1.usercontent.dev safe to connect a wallet?

This report does not record which wallet requests entry5300-js2024r1.usercontent.dev makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used entry5300-js2024r1.usercontent.dev?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 3 captures

URLScan · 2026-07-01 1 / 3 Used in the analysis Source file SHA-256: 17cdc6a2817af5037b9bc41defdb7ea0e93e326c0ce70d82881f53c030349f36 SHA-256 of the prepared copy given to the model: 88b45dc417059b542e2d99c784e13b9f9e62a01207edb36db8094cd1d3d958c5
SourceURLScan · 2026-07-01
Recorded
StateStored capture
HTTP status200
Final URLhttps://entry5300-js2024r1.usercontent.dev/
Position1 / 3
Open capture Source Report Wayback Download
All capture links and hashes (3)
Observed page title
Telegram Web
Automated brand references
Telegram
TLS Certificate
Issued by GoDaddy.com / GoDaddy TLS Intermediate CA DV - R1v1 · stored validity ends in 149 days

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Telegram report ↗
Google Safe Browsing Flagged Social engineering checked Nov 8, 2026
IP Reputation Netherlands178.128.255.27 abuse score 0/100 0 reports checked Nov 8, 2026
Registrar (base domain) GoDaddy US(US)
Abuse contact["abuse@godaddy.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for usercontent.dev →
Registration (base domain)usercontent.dev · Created Apr 15, 2019 — Expires Apr 15, 2027
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 7, 2026
DOM Analysisanalyzed Nov 8, 2026score 10/1001 brand signal
Submitted URLhttp://entry5300-js2024r1.usercontent.dev/
Favicon Hash
ICANN OVERSIGHT Registration: usercontent.dev

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain usercontent.dev behind this subdomain, 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

Resolved IP
Netherlands178.128.255.27
Network ASN
AS14061
Organization
DigitalOcean, LLC
Observed location
NetherlandsAmsterdam, NL
Server header
nginx/1.10.3

Nameservers 2

  • pdns11.domaincontrol.com
  • pdns12.domaincontrol.com

Location describes the IP network.

TLS certificate

Issuer
GoDaddy.com / GoDaddy TLS Intermediate CA DV - R1v1
Valid from
2026-09-20 11:32:44
Valid until
2027-04-06 11:32:44
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint666b1d783ec22978927e965dc357339f5e59ad2eec4466acefa9a85df8d0e5b8
Certificate names · 2 SANs
  • *.usercontent.dev
  • usercontent.dev

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

viewdns.info · 178.128.255.27rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
CRDF
ESET
VIPRE
Lionic
Sophos
Webroot
Emsisoft
Fortinet
Netcraft
SOCRadar
Kaspersky
Seclookup
Gridinsoft
Criminal IP
Yandex Safebrowsing
Google Safe Browsing
Forcepoint ThreatSeeker
Registration & observation details1

Availability observations

Last reachable observation

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

Captured network requests

Network requests: 23 SHA-256 hashes: 18 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-08 02:05 UTC.

Open this scan on URLScan 019f1efd-e0cb-7318-8a86-22fb69ba7159 ↗

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. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  2. Domain monitor · First collection record

    Reachable

Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
200
Probe value as recorded
200
Original source timestamp
2026-11-07 16:28:40
All retained availability observations2

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 03:00:36.000000
    Evidence SHA-256
    afbd4eca1bd7c33d30d9a8246145b08bf87529164004f8882634e998c784736b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 03:00:36
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 03:00:36.000000
    Evidence SHA-256
    afbd4eca1bd7c33d30d9a8246145b08bf87529164004f8882634e998c784736b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 03:00:36
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

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

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    entry5300-js2024r1.usercontent.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Google Safe Browsing · Automated brand label: Telegram · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 17/92
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • Automated brand label: Telegram
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. Cloudflare Radar

    Phishing

    View source
  2. Google Safe Browsing

    Threat flag recorded

    View source
  3. Added to PhishDestroy

    entry5300-js2024r1.usercontent.dev

    View source
  4. VirusTotal

    17/92 engine detections

    View source
  5. URLScan

    Malicious

    View source
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
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

entry5300-js2024r1.usercontent.dev

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 17 det. ChainPatrol URLQuery Google SB Flagged SSL Labs Stored certificate dates valid 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 & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

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 entry5300-js2024r1.usercontent.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

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

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 →
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.

Request a correction or appeal How PhishDestroy works
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/entry5300-js2024r1.usercontent.dev"
  title="PhishDestroy threat report for entry5300-js2024r1.usercontent.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>