Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 20. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
tg-jsnq.com favicon

tg-jsnq.com

In short

tg-jsnq.com is a phishing page detected by PhishDestroy on 2026-10-25.

“WhatsApp Web”

Review the evidence
Registrar
Hosting Concepts
Resolved IP
161.248.14.193
Registered
Mar 22, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 20/92 Spamhaus DBL: phishing domain Stored blocklist matches: 1 Google Safe Browsing: threat flag recorded
VirusTotal
20 / 92
engine detections ·
OTX
4
community references
Cloudflare Radar
Phishing
Page captures
8
open gallery
Domain age
217 days
Reports sent
1
view timeline
OTX: 4 refs Oct 25, 2026 1 Report Sent
X Telegram API

Analysis

Domain summary

tg-jsnq.com is a phishing page detected by PhishDestroy on 2026-10-25. Risk: critical (100/100). Registrar: Hosting Concepts. Status: Last known active. Hosting: Iens Technology Pte. LTD. PhishDestroy sent 1 abuse report. VirusTotal: 20/92 engines flag it. Google Safe Browsing flags it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
20 / 92
OTX
4 community refs
Page captures
8
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy lists tg-jsnq.com as a suspicious domain. The recorded page title is "WhatsApp Web" and the domain was first observed on 2026-10-25.

How the scam works

The listing does not confirm a specific fraud mechanism. Social‑engineering pages often mimic popular services to lure users into entering credentials or clicking malicious links.

Evidence

VirusTotal reported 20 detections from 92 engines on 2026-10-25, including phishing labels. Google Safe Browsing flagged the site for SOCIAL_ENGINEERING on the same date. OpenPhish and Spamhaus DBL listed the domain as phishing on 2026-10-25. urlscan and Cloudflare Radar both returned malicious verdicts with phishing tags on 2026-10-25.

Infrastructure

The domain was registered on 2026-03-22 with Hosting Concepts B.V. d/b/a Registrar.eu and resolves to IP 161.248.14.193, a network owned by Iens Technology Pte. Ltd in Malaysia. Nameservers are ns1.dyna-ns.net and ns2.dyna-ns.net. The TLS certificate was valid from 2026-09-15 to 2026-12-14.

What to do

Avoid visiting or interacting with tg-jsnq.com. If credentials were entered, change them elsewhere and scan devices. Organizations should block the domain and review proxy or DNS logs for related activity.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportURLQuery reportStored capture screenshotCloudflare Radar screenshot (2026-10-25T04:37:53Z)URLQuery screenshotURLScan screenshot (2026-10-24T14:46:03Z)URLScan capture reportURLScan screenshot (2026-10-25T01:01:55Z)URLScan capture reportURLScan screenshot (2026-10-25T04:46:56Z)URLScan capture reportURLScan screenshot (2026-10-25T05:14:11Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 20 / 92 · Google Safe Browsing: flagged · OTX 4 references 9 sources

VirusTotal

20 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
43
Malicious
18
Suspicious
2
Undetected
29

Vendor labels

DNS8
suspicious
ESET
phishing
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
SOCRadar
phishing
Kaspersky
phishing
LevelBlue
phishing
Gridinsoft
suspicious
MalwareURL
phishing
BitDefender
phishing
alphaMountain.ai
phishing
Google Safe Browsing
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Tags

  • dga

Categories

Sophos
phishing and fraud
Webroot
Phishing and Other Frauds
alphaMountain.ai
Phishing (alphaMountain.ai)

Created

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.dyna-ns.net
  • TTL, seconds
    300
    Type
    A
    Value
    161.248.14.193
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    hostmaster.tg-jsnq.com
    Value
    ns1.dyna-ns.net
  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.dyna-ns.net

DNS records observed

JARM fingerprint

3fd3fd0003fd3fd00042d43d0000002059a3b916699461c5923779b77cf06b

Certificate

Subject alternative names
  • tg-jsnq.com
Issuer
Let's Encrypt / YR2
Serial
550cf7378ae492b25e5c9fd3d8bdc09ade9
SHA-256
8456ce39304b0cbf10da2b06ee89c4abec2053ba34f96ca92303bc61c0bec1a9
Subject
tg-jsnq.com
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Expiration
Registration
Registrar expiration
Last RDAP database update
Registrar
Hosting Concepts B.V. d/b/a Registrar.eu
Registrar IANA ID
1647
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 18,
    "suspicious": 2,
    "undetected": 29
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "suspicious",
    "MalwareURL": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Google Safe Browsing": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Created
2026-03-22T00:00:00Z
Updated
2026-03-22T00:00:00Z
First seen
2026-03-22T07:33:22Z
DNS records
[
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "161.248.14.193"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.tg-jsnq.com",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.dyna-ns.net"
    }
]
Dns at
2026-10-25T09:32:08Z
Jarm
3fd3fd0003fd3fd00042d43d0000002059a3b916699461c5923779b77cf06b
Certificate
{
    "san": [
        "tg-jsnq.com"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "550cf7378ae492b25e5c9fd3d8bdc09ade9",
    "sha256": "8456ce39304b0cbf10da2b06ee89c4abec2053ba34f96ca92303bc61c0bec1a9",
    "subject": "tg-jsnq.com",
    "valid_to": "2026-12-14T23:15:16Z",
    "valid_from": "2026-09-15T23:15:17Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-03-22T06:28:04Z",
        "registration": "2026-03-22T06:28:04Z",
        "registrar expiration": "2027-03-22T06:28:04Z",
        "last update of RDAP database": "2026-10-24T15:11:31Z"
    },
    "registrar": "Hosting Concepts B.V. d/b/a Registrar.eu",
    "registrar_iana_id": "1647"
}
Separate source record · 18 malicious + 2 suspicious / 92 · 2026-10-25 09:31:15 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-25T09:31:15Z
fetched_at
2026-10-25T16:50:23Z
stats
{"timeout":0,"harmless":43,"malicious":18,"suspicious":2,"undetected":29}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Report ID

b0768da8-d8fd-41d5-a723-ec29325c8489

Final URL

https://tg-jsnq.com/

HTTP response

200

Navigation history

  • URL
    https://tg-jsnq.com/
    Status
    200

DOM structure hash

ab411995d2753ec19061935678370a05f147c2e3b2a420bd445ae6007d098d16

Document hash

82aa84b7cdb5fc0c300de364f996bb963a308c530a7d34ca117269e6cef4d764

Phishing classifier result

  • phishing

URL risk categories

  • Phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    tg-jsnq.com
    Type
    A
    Value
    161.248.14.193

DNSSEC valid

No

IP address

161.248.14.193

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Hosting Concepts B.V. d/b/a Registrar.eu
Registered
Updated
Expires
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
Original source fields · JSON
Uuid
b0768da8-d8fd-41d5-a723-ec29325c8489
Final url
https://tg-jsnq.com/
Status
200
History
[
    {
        "url": "https://tg-jsnq.com/",
        "status": 200
    }
]
DOM structure hash
ab411995d2753ec19061935678370a05f147c2e3b2a420bd445ae6007d098d16
Document hash
82aa84b7cdb5fc0c300de364f996bb963a308c530a7d34ca117269e6cef4d764
Phishing v2
[
    "phishing"
]
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "tg-jsnq.com",
        "type": "A",
        "value": "161.248.14.193"
    }
]
Dnssec valid
false
Ip
161.248.14.193
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Hosting Concepts B.V. d/b/a Registrar.eu",
    "created": "2026-03-22T06:28:04Z",
    "updated": "2026-03-22T06:28:07Z",
    "expires": "2027-03-22T06:28:04Z",
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}

Google Safe Browsing

Threat flag recorded

Open report

Spamhaus DBL

phishing domain

URLScan

Malicious

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a1715d-9853-72bc-acac-e9011ea1cc85

Final URL

https://tg-jsnq.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://tg-jsnq.com/
    From
    http://tg-jsnq.com/
    Status
    307

IP address

161.248.14.193

Contacted domains

  • api.ipregistry.co

Contacted IP addresses

  • 104.18.27.170
  • 161.248.14.193

Autonomous systems (ASN)

  • 13335
  • 4907

Server countries

  • MY

Document hash

82aa84b7cdb5fc0c300de364f996bb963a308c530a7d34ca117269e6cef4d764

Script hashes

  • 3e7e5d1b4c93783ad42e96590f6a1c0a732254475f2035cd2affc2318cc735cb
  • f11056f5e8729994ffdde938f4a48d7cd50422782b24a50f1871d67f31ab1595
  • 7118675016330b13df45bf83dc72e5d2d3a01f62360283b450422f2bf0f612d4

JavaScript globals

  • __VUE_INSTANCE_SETTERS__
  • __VUE_SSR_SETTERS__
  • __INTLIFY_PROD_DEVTOOLS__
  • __INTLIFY_JIT_COMPILATION__
  • __INTLIFY_DROP_MESSAGE_COMPILER__
  • __VUE_I18N_FULL_INSTALL__
  • __VUE_I18N_LEGACY_API__
  • __resetUuid
  • __VUE__
  • __vueuse_ssr_handlers__

Browser storage keys

  • ws_uuid
  • visitor_country_code
  • visitor_country_code_expiry

TLS session and certificate

Subject alternative names
  • tg-jsnq.com
Cipher
AES_128_GCM
Issuer
YR2
Subject
tg-jsnq.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

216

Registered domain age, days

216

Certificate age, days

39

Certificate validity, days

89

Page requests

13

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
96
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • whatsapp
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • WhatsApp
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
nginx
Content-type
text/html
Strict-transport-security
max-age=31536000
Original source fields · JSON
Uuid
01a1715d-9853-72bc-acac-e9011ea1cc85
Final url
https://tg-jsnq.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://tg-jsnq.com/",
        "from": "http://tg-jsnq.com/",
        "status": 307
    }
]
Ip
161.248.14.193
Contacted domains
[
    "api.ipregistry.co"
]
Contacted IP addresses
[
    "104.18.27.170",
    "161.248.14.193"
]
Asns
[
    "13335",
    "4907"
]
Countries
[
    "MY"
]
Document hash
82aa84b7cdb5fc0c300de364f996bb963a308c530a7d34ca117269e6cef4d764
Script hashes
[
    "3e7e5d1b4c93783ad42e96590f6a1c0a732254475f2035cd2affc2318cc735cb",
    "f11056f5e8729994ffdde938f4a48d7cd50422782b24a50f1871d67f31ab1595",
    "7118675016330b13df45bf83dc72e5d2d3a01f62360283b450422f2bf0f612d4"
]
Globals
[
    "__VUE_INSTANCE_SETTERS__",
    "__VUE_SSR_SETTERS__",
    "__INTLIFY_PROD_DEVTOOLS__",
    "__INTLIFY_JIT_COMPILATION__",
    "__INTLIFY_DROP_MESSAGE_COMPILER__",
    "__VUE_I18N_FULL_INSTALL__",
    "__VUE_I18N_LEGACY_API__",
    "__resetUuid",
    "__VUE__",
    "__vueuse_ssr_handlers__"
]
Storage keys
[
    "ws_uuid",
    "visitor_country_code",
    "visitor_country_code_expiry"
]
Tls
{
    "san": [
        "tg-jsnq.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR2",
    "subject": "tg-jsnq.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-14T23:15:16Z",
    "valid_from": "2026-09-15T23:15:17Z"
}
Domain age days
216
Apex age days
216
Tls age days
39
Tls valid days
89
Requests
13
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 96,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "whatsapp"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "WhatsApp"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html",
    "strict-transport-security": "max-age=31536000"
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a17093-f878-7359-a99d-8e319b333b4d
score
null
malicious
null
result_at
null
enriched_at
2026-10-25T09:11:39Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-25 10:11:39"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

4 community references

Open report

PhishDestroy DOM

100 / 100 · heuristic score · 1 brand references · 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
tg-jsnq.com — Suspicious Domain
ai_description
tg-jsnq.com is flagged by PhishDestroy as a suspicious site impersonating WhatsApp Web, showing social‑engineering risk.
ai_generated_at
2026-10-25T16:53:02Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider 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: 22 fields

Mail configuration

SPF lookups
0

CAA records

Domain
tg-jsnq.com

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
1
Average page size, bytes
2139

Page title and metadata

Page title
WhatsApp Web

Trackers

Requests
9

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
317
TLS
270
Waiting
259
Connection
259
Download
1
Response time, ms
1106

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 3306

Carbon estimate

Bytes
4078
CO₂, grams
0.0001
Cleaner than, %
91

DNS servers

Nameservers
  • IP address
    162.159.27.158
    Host
    ns1.dyna-ns.net
  • IP address
    162.159.25.5
    Host
    ns2.dyna-ns.net
DNS zone
tg-jsnq.com

Location

IP address
161.248.14.193
ASN
4907
Organization
Iens Technology Pte. LTD
City
Kuala Lumpur
Country
MY

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
tg-jsnq.com

DNS records

A
  • 161.248.14.193
NS
  • ns2.dyna-ns.net
  • ns1.dyna-ns.net
SOA
Primary nameserver
ns1.dyna-ns.net
Hostmaster
hostmaster.tg-jsnq.com
Serial
2026032102
Refresh, seconds
16384
Retry, seconds
2048
Expiry, seconds
1209600
Minimum TTL, seconds
300

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000
Observation
HSTS header does not include all subdomains.

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
max-age=31536000
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
161.248.14.193
IP version
4

Redirects

Redirect chain
  • https://tg-jsnq.com

Registration record

Registrar
Hosting Concepts B.V. d/b/a Registrar.eu
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

HTTP headers

Response headers
Server
nginx
Content-type
text/html
Strict-transport-security
max-age=31536000
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "tg-jsnq.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-25T04:34:28Z",
    "first": "2026-10-25T04:34:28Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 2139
}
Page title and metadata
{
    "title": "WhatsApp Web"
}
Trackers
{
    "requests": 9
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 317,
        "tls": 270,
        "wait": 259,
        "connect": 259,
        "download": 1
    },
    "response_ms": 1106
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        3306
    ]
}
Carbon
{
    "bytes": 4078,
    "co2_grams": 0.0001,
    "cleaner_than": 91
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.27.158",
            "host": "ns1.dyna-ns.net"
        },
        {
            "ip": "162.159.25.5",
            "host": "ns2.dyna-ns.net"
        }
    ],
    "zone": "tg-jsnq.com"
}
Location
{
    "ip": "161.248.14.193",
    "asn": "4907",
    "org": "Iens Technology Pte. LTD",
    "city": "Kuala Lumpur",
    "country": "MY"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "tg-jsnq.com"
}
DNS records
{
    "A": [
        "161.248.14.193"
    ],
    "NS": [
        "ns2.dyna-ns.net",
        "ns1.dyna-ns.net"
    ],
    "SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.tg-jsnq.com\", \"serial\": 2026032102, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000",
    "message": "HSTS header does not include all subdomains."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31536000",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "161.248.14.193",
    "family": 4
}
Redirects
{
    "chain": [
        "https://tg-jsnq.com"
    ]
}
Registration record
{
    "registrar": "Hosting Concepts B.V. d/b/a Registrar.eu",
    "created": "2026-03-22T06:28:04Z",
    "updated": "2026-03-22T06:28:07Z",
    "expires": "2027-03-22T06:28:04Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html",
        "strict-transport-security": "max-age=31536000"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Phishing Security threats
View full Cloudflare Radar report

Questions about tg-jsnq.com

Is tg-jsnq.com legit?

No. PhishDestroy classifies tg-jsnq.com as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-25. VirusTotal: 20/92 engines flag it. Google Safe Browsing flags it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is tg-jsnq.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on tg-jsnq.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used tg-jsnq.com?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesOpenPhish · PhishDestroy 2
OpenPhish Listed View source
PhishDestroy PhishDestroy list View source

Last checked

Stored Capture · 8 captures

Primary capture 1 / 8
SourcePrimary capture
Recorded
StateStored capture
HTTP statusNot recorded for this capture
Final URLNot recorded for this capture
Position1 / 8
Open capture Wayback Download
All capture links and hashes (8)

Domain details

Domain
Google Safe Browsing Flagged Social engineering checked Oct 25, 2026
IP Reputation abuse score 0/100 0 reports checked Oct 25, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Hosting Concepts US(US)
Abuse contactabuse@cloudbays.com, abuse@registrar.eu
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for tg-jsnq.com →
RegistrationCreated Mar 22, 2026 (217d) — Expires Mar 22, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 100/1001 brand signal
Submitted URLhttp://tg-jsnq.com/?… query redacted
Favicon Hash
Case ID
Observed page title
WhatsApp Web
Automated brand references
WhatsApp
TLS Certificate
Issued by YR2 · stored validity ends in 49 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
161.248.14.193
Network ASN
AS4907
Organization
Iens Technology Pte. LTD
Observed location
Kuala Lumpur, MY
Server header
nginx

Nameservers 2

  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

Location describes the IP network.

TLS certificate

Issuer
YR2
Valid from
2026-09-15 23:15:17
Valid until
2026-12-14 23:15:16
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint8456ce39304b0cbf10da2b06ee89c4abec2053ba34f96ca92303bc61c0bec1a9
Certificate names · 1 SAN
  • tg-jsnq.com

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

viewdns.info · 161.248.14.193rapiddns.io

Latest Classified Outcome 2026-10-25 12:22:48 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Unknown Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-25 12:22:48 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-25 04:43:22 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

20 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 20 detections
alphaMountain.ai
BitDefender
CyRadar
DNS8
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
Kaspersky
LevelBlue
Lionic
MalwareURL
Netcraft
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of tg-jsnq.com · checked Oct 25, 2026

77
Needs Work
Performance
FCP
3.17 s
First Contentful Paint
LCP
3.95 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
2 ms
Total Blocking Time
SI
5.84 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://tg-jsnq.com/
Final URL: https://tg-jsnq.com/
WhatsApp Web
Response
HTTP 200
HTML body
4.0 KB
Compressed
1.3 KB
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Content-Encoding: gzip
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 11
Alt-Svc
quic=":443"; h3=":443"; h3-29=":443"; h3-27=":443";h3-25=":443"; h3-T050=":443"; h3-Q050=":443";h3-Q049=":443";h3-Q048=":443"; h3-Q046=":443"; h3-Q043=":443"
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Sun, 25 Oct 2026 04:35:36 GMT
Etag
W/"6a9f2ca5-fee"
Last-Modified
Mon, 07 Sep 2026 21:29:09 GMT
Server
nginx
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

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

Check for cloaking

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

Page titles differ

alive_content: raw=ok; http=200; via=https_proxy; server=Caddy

Browser
WhatsApp Web
Crawler
tg-jsnq.com
tg-jsnq.com
Stored observation history5

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

    content_served

  2. VirusTotal · Detection count

    19→20

    Engines added
    MalwareURL
    Engines removed
    None recorded
    Recorded vendor total
    20
  3. VirusTotal · Detection count

    18→19

    Engines added
    CyRadar
    Engines removed
    None recorded
    Recorded vendor total
    19
  4. VirusTotal · Detection count

    17→18

    Engines added
    LevelBlue · SOCRadar
    Engines removed
    CyRadar
    Recorded vendor total
    18
  5. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

All retained availability observations5

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_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:22:48.000000
    Evidence SHA-256
    a1d4152253a1b8e75015e3efae63275c552bb3be285deb48d811a4c420028e95
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:22:48
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:22:48.000000
    Evidence SHA-256
    a1d4152253a1b8e75015e3efae63275c552bb3be285deb48d811a4c420028e95
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:22:48
    Evidence reason
    alive_content
  3. 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-10-25 05:43:22.000000
    Evidence SHA-256
    b902264295124558f99fa4f7015f49d22e7154974735b1f84be314ecdcb88241
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 05:43:22
    Evidence reason
  4. 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-10-25 05:43:22.000000
    Evidence SHA-256
    b902264295124558f99fa4f7015f49d22e7154974735b1f84be314ecdcb88241
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 05:43:22
    Evidence reason
  5. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 05:38:40.309689
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Recorded activity

8 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    Threat flag recorded

    View source
  3. VirusTotal

    20/92 engine detections

    View source
  4. Abuse report sent

    PD-20261025-F34C3C

    abuse@cloudbays.com
  5. URLScan

    Page captured

    View source
  6. Cloudflare Radar

    Phishing

    View source
  7. Wayback Machine

    Page archived

    View source
  8. Added to PhishDestroy

    tg-jsnq.com

    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

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 20 det. ChainPatrol URLQuery 2 det. Google SB Flagged SSL Labs Stored certificate dates valid CF Radar Malicious OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261025-F34C3C Recipient: abuse@cloudbays.com
Page title stored with report: WhatsApp
PDF notice generated Notice text archived (859 chars)
Abuse notice text as sent to the provider 
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (US):
18 U.S.C. § 1343 - Wire Fraud
18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA)
15 U.S.C. § 45 - FTC Act (Deceptive Practices)
Federal laws prohibit wire fraud, computer fraud, and deceptive business practices.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
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?

6 evidence signal groups linked 1 stored notification records 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.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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 →.

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.

  • 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 tg-jsnq.com)
  • 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/tg-jsnq.com"
  title="PhishDestroy threat report for tg-jsnq.com"
  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>