Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 9/92 engines flagged. malicious: 9. suspicious: 0. Analysis time (as stored): 2026-11-07T12:53:29Z. Retrieved (as stored): 2026-11-08T07:52:49Z. Listed by external blocklists: OpenPhish. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
js8713.com favicon

js8713.com

In short

PhishDestroy first recorded js8713.com on 2026-11-08. Stored VirusTotal result: 9/92 engines flagged. malicious: 9. suspicious: 0. Analysis time (as stored): 2026-11-07T12:53:29Z. Retrieved (as stored): 2026-11-08T07:52:49Z. Listed by external blocklists: OpenPhish.

“页面未找到 - 404错误”

Review the evidence
Registrar
NetherlandsHosting Concepts
Resolved IP
Hong Kong SAR China168.76.230.166Freenet
Registered
Jun 27, 2026
First observed
Nov 8, 2026
PhishDestroy assessment Critical
90/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 9/92 Spamhaus DBL: spam domain Stored blocklist matches: 1
VirusTotal
9 / 92
engine detections ·
Blocklist matches
1
OpenPhish
OTX
3
community references
URLScan
Malicious
engine verdict · score 19
Page captures
4
open gallery
Domain age
133 days
registered 2026-06-27 according to WHOIS · source data differ
OTX: 3 refs Nov 8, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded js8713.com on 2026-11-08. Stored VirusTotal result: 9/92 engines flagged. malicious: 9. suspicious: 0. Analysis time (as stored): 2026-11-07T12:53:29Z. Retrieved (as stored): 2026-11-08T07:52:49Z. Listed by external blocklists: OpenPhish. Risk: critical (90/100). Registrar: Hosting Concepts. Status: Last known active. Hosting: Freenet. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
9 / 92
Blocklist matches
1
Hosting
Hong Kong SAR China168.76.230.166Freenet
Registrar
NetherlandsHosting Concepts
Registered
Jun 27, 2026
OTX
3 community refs
Page captures
4
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for js8713.com. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 9 / 92 · OTX 3 references 6 sources

VirusTotal

9 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
50
Malicious
9
Suspicious
0
Undetected
33

Vendor labels

G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Tags

  • dga

Categories

Google
gambling
Sophos
phishing and fraud
Webroot
Phishing and Other Frauds
alphaMountain.ai
Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
phishing and other frauds

Created

Updated

First seen

DNS records

  • TTL, seconds
    600
    Type
    A
    Value
    156.239.65.40
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns1.domainnamedns.com
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns2.domainnamedns.com
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns3.domainnamedns.com
  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    support.namens.net
    Value
    ns1.domainnamedns.com
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns4.domainnamedns.com

DNS records observed

JARM fingerprint

3fd3fd0003fd3fd00042d43d0000002059a3b916699461c5923779b77cf06b

Certificate

Subject alternative names
  • 115js.cc
  • 28jsjs.com
  • 2js.info
  • 2jsh.com
  • 333jsc.com
  • 545js.com
  • 644js.com
  • 6js.info
  • 8730js.com
  • 99js.org
Issuer
Let's Encrypt / YR2
Serial
52116ae44501cff4716b6f0a15afb28048a
SHA-256
c615b50ae961ea80d3231338749a445dd75c98497ab9e3b5e1207130edb01497
Subject
115js.cc
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": 50,
    "malicious": 9,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "Google": "gambling",
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Created
2025-03-30T00:00:00Z
Updated
2026-03-31T00:00:00Z
First seen
2025-04-02T16:07:04Z
DNS records
[
    {
        "ttl": 600,
        "type": "A",
        "value": "156.239.65.40"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns1.domainnamedns.com"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns2.domainnamedns.com"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns3.domainnamedns.com"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "support.namens.net",
        "value": "ns1.domainnamedns.com"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns4.domainnamedns.com"
    }
]
Dns at
2026-11-07T12:53:48Z
Jarm
3fd3fd0003fd3fd00042d43d0000002059a3b916699461c5923779b77cf06b
Certificate
{
    "san": [
        "115js.cc",
        "28jsjs.com",
        "2js.info",
        "2jsh.com",
        "333jsc.com",
        "545js.com",
        "644js.com",
        "6js.info",
        "8730js.com",
        "99js.org"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "52116ae44501cff4716b6f0a15afb28048a",
    "sha256": "c615b50ae961ea80d3231338749a445dd75c98497ab9e3b5e1207130edb01497",
    "subject": "115js.cc",
    "valid_to": "2027-01-28T21:41:32Z",
    "valid_from": "2026-10-30T21:41:33Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-06-27T22:07:43Z",
        "registration": "2026-06-27T22:07:43Z",
        "registrar expiration": "2027-06-27T22:07:43Z",
        "last update of RDAP database": "2026-11-04T09:19:23Z"
    },
    "registrar": "Hosting Concepts B.V. d/b/a Registrar.eu",
    "registrar_iana_id": "1647"
}
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
9
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","CyRadar","Forcepoint ThreatSeeker","Fortinet","G-Data","Lionic","Sophos","Webroot"]
observed_at
2026-11-07 12:53:29
checked_at
2026-11-08 08:52:49
fetched_at
2026-11-08 07:52:50
time_basis
as stored; legacy timezone not established

Spamhaus DBL

spam domain

URLScan

Malicious · engine verdict · score 19

SHA-256 115dc878fdab3fdfd4a991d71534b9ecf6a1abcf09f1b067fdac8adadd55cfda

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a1b97a-ddfb-744d-8d05-d30517af1de0

Final URL

https://www.js8713.com/404.html

HTTP response

200

Redirect type

same-domain

Redirects

  • To
    https://www.js8713.com/natsu/index.html
    From
    http://www.js8713.com/natsu/index.html
    Status
    307
  • To
    https://www.js8713.com/404.html
    From
    https://www.js8713.com/natsu/index.html
    Status
    302

IP address

168.76.230.166

Contacted IP addresses

  • 168.76.230.166

Autonomous systems (ASN)

  • 137951

Server countries

  • ZA

Document hash

115dc878fdab3fdfd4a991d71534b9ecf6a1abcf09f1b067fdac8adadd55cfda

TLS session and certificate

Subject alternative names
  • 016js.com
  • www.016js.com
Cipher
AES_256_GCM
Issuer
YR1
Subject
016js.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

436

Differs from the registration date in WHOIS (2026-06-27), which gives 133 days on the scan date 2026-11-08. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1362

Differs from the registration date in WHOIS (2026-06-27), which gives 133 days on the scan date 2026-11-08. The two sources disagree; both values are kept as recorded.

Certificate age, days

0

Certificate validity, days

89

Page requests

2

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
19
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
nginx
Content-type
text/html
Strict-transport-security
max-age=31536000
Original source fields · JSON
Uuid
01a1b97a-ddfb-744d-8d05-d30517af1de0
Final url
https://www.js8713.com/404.html
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://www.js8713.com/natsu/index.html",
        "from": "http://www.js8713.com/natsu/index.html",
        "status": 307
    },
    {
        "to": "https://www.js8713.com/404.html",
        "from": "https://www.js8713.com/natsu/index.html",
        "status": 302
    }
]
Ip
168.76.230.166
Contacted IP addresses
[
    "168.76.230.166"
]
Asns
[
    "137951"
]
Countries
[
    "ZA"
]
Document hash
115dc878fdab3fdfd4a991d71534b9ecf6a1abcf09f1b067fdac8adadd55cfda
Tls
{
    "san": [
        "016js.com",
        "www.016js.com"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR1",
    "subject": "016js.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-02-06T00:51:19Z",
    "valid_from": "2026-11-08T00:51:20Z"
}
Domain age days
436

Differs from the registration date in WHOIS (2026-06-27), which gives 133 days on the scan date 2026-11-08. The two sources disagree; both values are kept as recorded.

Apex age days
1362

Differs from the registration date in WHOIS (2026-06-27), which gives 133 days on the scan date 2026-11-08. The two sources disagree; both values are kept as recorded.

Tls age days
0
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 19,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
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
01a1b97a-ddfb-744d-8d05-d30517af1de0
score
null
malicious
null
result_at
null
enriched_at
2026-11-08T09:11:55Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-11-08 10:11:55"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

3 community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

d3b14338-ed93-4391-ab2c-e13dfb3a01c8

Final URL

https://www.js8713.com/404.html

HTTP response

200

Redirect type

subdomain

Navigation history

  • URL
    https://js8713.com/
    Status
    301
  • URL
    https://www.js8713.com/
    Status
    302
  • URL
    https://www.js8713.com/404.html
    Status
    200

DOM structure hash

06c29792480dadae255cbaaf0a21c87a50749e7264d31ca1fefcca386d861f99

Document hash

115dc878fdab3fdfd4a991d71534b9ecf6a1abcf09f1b067fdac8adadd55cfda

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    js8713.com
    Type
    A
    Value
    168.76.230.166
  • Name
    www.js8713.com
    Type
    A
    Value
    168.76.230.166

DNSSEC valid

No

IP address

127.0.1.8

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

Registration record

Registrar
Hosting Concepts B.V. d/b/a Registrar.eu
Registered
Updated
Expires
Nameservers
  • ns1.domainnamedns.com
  • ns2.domainnamedns.com
Original source fields · JSON
Uuid
d3b14338-ed93-4391-ab2c-e13dfb3a01c8
Final url
https://www.js8713.com/404.html
Status
200
Redirected
subdomain
History
[
    {
        "url": "https://js8713.com/",
        "status": 301
    },
    {
        "url": "https://www.js8713.com/",
        "status": 302
    },
    {
        "url": "https://www.js8713.com/404.html",
        "status": 200
    }
]
DOM structure hash
06c29792480dadae255cbaaf0a21c87a50749e7264d31ca1fefcca386d861f99
Document hash
115dc878fdab3fdfd4a991d71534b9ecf6a1abcf09f1b067fdac8adadd55cfda
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "js8713.com",
        "type": "A",
        "value": "168.76.230.166"
    },
    {
        "name": "www.js8713.com",
        "type": "A",
        "value": "168.76.230.166"
    }
]
Dnssec valid
false
Ip
127.0.1.8

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

Registration record
{
    "registrar": "Hosting Concepts B.V. d/b/a Registrar.eu",
    "created": "2026-06-27T22:07:43Z",
    "updated": "2026-06-27T22:07:50Z",
    "expires": "2027-06-27T22:07:43Z",
    "nameservers": [
        "ns1.domainnamedns.com",
        "ns2.domainnamedns.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

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: 24 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
8
Archived days
11
Snapshots per day
0
Average page size, bytes
3069

Page title and metadata

Page title
页面未找到 - 404错误

Trackers

Requests
2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
301
Request timings, ms
DNS
594
TLS
204
Waiting
185
Connection
185
Download
0
Response time, ms
1168

TLS connection

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

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
3841
CO₂, grams
0.0001
Cleaner than, %
92

DNS servers

Nameservers
  • IP address
    54.151.142.119
    Host
    ns3.domainnamedns.com
  • IP address
    216.106.185.75
    Host
    ns1.domainnamedns.com
  • IP address
    67.220.72.51
    Host
    ns4.domainnamedns.com
  • IP address
    38.114.114.183
    Host
    ns2.domainnamedns.com
DNS zone
js8713.com

Location

IP address
168.76.230.166
ASN
137951
Organization
Freenet
City
Tseung Kwan O
Country
HK

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
js8713.com

DNS records

A
  • 168.76.230.166
NS
  • ns3.domainnamedns.com
  • ns2.domainnamedns.com
  • ns4.domainnamedns.com
  • ns1.domainnamedns.com
SOA
Primary nameserver
ns1.domainnamedns.com
Hostmaster
support.namens.net
Serial
1794063022
Refresh, seconds
3600
Retry, seconds
1800
Expiry, seconds
1209600
Minimum TTL, seconds
180

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
168.76.230.166
IP version
4

Redirects

Redirect chain
  • https://js8713.com
  • https://www.js8713.com/
  • /404.html
Count
2

Subdomains

Count
2
Subdomains
  • m.js8713.com
  • www.js8713.com

Technology stack

Technologies
  • Nginx
  • HSTS

Page links

Internal links
1

Registration record

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

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
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2025-07-12T02:42:51Z",
    "first": "2017-04-21T09:16:21Z",
    "changes": 8,
    "days_archived": 11,
    "scans_per_day": 0,
    "avg_page_bytes": 3069
}
Page title and metadata
{
    "title": "页面未找到 - 404错误"
}
Trackers
{
    "requests": 2
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 301,
    "timings": {
        "dns": 594,
        "tls": 204,
        "wait": 185,
        "connect": 185,
        "download": 0
    },
    "response_ms": 1168
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 3841,
    "co2_grams": 0.0001,
    "cleaner_than": 92
}
Dns server
{
    "ns": [
        {
            "ip": "54.151.142.119",
            "host": "ns3.domainnamedns.com"
        },
        {
            "ip": "216.106.185.75",
            "host": "ns1.domainnamedns.com"
        },
        {
            "ip": "67.220.72.51",
            "host": "ns4.domainnamedns.com"
        },
        {
            "ip": "38.114.114.183",
            "host": "ns2.domainnamedns.com"
        }
    ],
    "zone": "js8713.com"
}
Location
{
    "ip": "168.76.230.166",
    "asn": "137951",
    "org": "Freenet",
    "city": "Tseung Kwan O",
    "country": "HK"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "js8713.com"
}
DNS records
{
    "A": [
        "168.76.230.166"
    ],
    "NS": [
        "ns3.domainnamedns.com",
        "ns2.domainnamedns.com",
        "ns4.domainnamedns.com",
        "ns1.domainnamedns.com"
    ],
    "SOA": "{\"nsname\": \"ns1.domainnamedns.com\", \"hostmaster\": \"support.namens.net\", \"serial\": 1794063022, \"refresh\": 3600, \"retry\": 1800, \"expire\": 1209600, \"minttl\": 180}"
}
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": "168.76.230.166",
    "family": 4
}
Redirects
{
    "chain": [
        "https://js8713.com",
        "https://www.js8713.com/",
        "/404.html"
    ],
    "count": 2
}
Subdomains
{
    "count": 2,
    "subdomains": [
        "m.js8713.com",
        "www.js8713.com"
    ]
}
Tech stack
{
    "technologies": [
        "Nginx",
        "HSTS"
    ]
}
Page links
{
    "internal_count": 1
}
Registration record
{
    "registrar": "Hosting Concepts B.V. d/b/a Registrar.eu",
    "created": "2026-06-27T22:07:43Z",
    "updated": "2026-06-27T22:07:50Z",
    "expires": "2027-06-27T22:07:43Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.domainnamedns.com",
        "ns2.domainnamedns.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html",
        "strict-transport-security": "max-age=31536000"
    }
}

Questions about js8713.com

Is js8713.com legit?

PhishDestroy rates js8713.com as critical risk (90/100) from the recorded evidence; it was first recorded on 2026-11-08. Stored VirusTotal result: 9/92 engines flagged. malicious: 9. suspicious: 0. Analysis time (as stored): 2026-11-07T12:53:29Z. Retrieved (as stored): 2026-11-08T07:52:49Z. Listed by external blocklists: OpenPhish. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is js8713.com safe to connect a wallet?

This report does not record which wallet requests js8713.com 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 js8713.com?

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 matchesOpenPhish · PhishDestroy · no match in the other 10 2
OpenPhish Listed View source
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 4 captures

URLScan · 2026-11-08 1 / 4
SourceURLScan · 2026-11-08
Recorded
StateStored capture
HTTP status200
Final URLhttps://www.js8713.com/404.html
Position1 / 4
Open capture Source Report Wayback Download
All capture links and hashes (4)

Domain details

Domain
IP Reputation Hong Kong SAR China168.76.230.166 abuse score 0/100 0 reports checked Nov 8, 2026
OTX tags 2026-11activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Hosting Concepts NL(NL)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for js8713.com →
RegistrationCreated Jun 27, 2026 (133d) — Expires Jun 27, 2027
Registrant countryChina VirusTotal WHOIS
Registrant37bfbc24cafea5d2 VirusTotal WHOIS
WHOIS statusclientTransferProhibited
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedNov 8, 2026
Submitted URLhttp://js8713.com/natsu/index.html
Favicon Hash
Observed page title
页面未找到 - 404错误
TLS Certificate
Issued by YR1 · stored validity ends in 89 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Hong Kong SAR China168.76.230.166
Network ASN
AS137951
AS name
ASLINE-AS-AP - ASLINE LIMITED, HK
Organization
Freenet
Observed location
Hong Kong SAR ChinaTseung Kwan O, HK
Server header
nginx

Nameservers 2

  • ns1.domainnamedns.com
  • ns2.domainnamedns.com

SOA

  • nsname: ns1.domainnamedns.com
  • hostmaster: support.namens.net
  • serial: 1794063022
  • refresh: 3600
  • retry: 1800
  • expire: 1209600
  • minttl: 180

Location describes the IP network.

TLS certificate

Issuer
YR1
Valid from
2026-11-08 00:51:20
Valid until
2027-02-06 00:51:19
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintc615b50ae961ea80d3231338749a445dd75c98497ab9e3b5e1207130edb01497
Certificate names · 2 SANs
  • 016js.com
  • www.016js.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 · 168.76.230.166rapiddns.io

Latest Classified Outcome 2026-11-08 11:00:53 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-08 11:00:53 UTC
RDAP registration
Observed timeline last reachable: 2026-11-08 11:00:53 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.
Recorded subdomains2

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • m.js8713.comDomain record
  • www.js8713.comDomain record
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

9 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
G-Data
Lionic
Sophos
CyRadar
Webroot
Fortinet
BitDefender
alphaMountain.ai
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of js8713.com · checked Nov 8, 2026

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

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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: 2 SHA-256 hashes: 2 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 07:40 UTC.

Open this scan on URLScan 01a1b97a-ddfb-744d-8d05-d30517af1de0 ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
页面未找到 - 404错误
Crawler
301 Moved Permanently
js8713.com
Stored observation history1

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

    redirected

    http_redirect

All retained availability observations4

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_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 12:00:53.000000
    Evidence SHA-256
    9806ded3c27d4073bec84e6b6e54ef39ce856c39f1d36152deff9d401c57f2e5
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-08 12:00:53
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 12:00:53.000000
    Evidence SHA-256
    9806ded3c27d4073bec84e6b6e54ef39ce856c39f1d36152deff9d401c57f2e5
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-08 12:00:53
    Evidence reason
    redirect
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 11:22:05.004741
    Evidence SHA-256
    2b635c6648ba6e529b842e210489cc0cc6e9715da198da3a1b40fdbd66628b9b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-08 11:22:05.004741
    Evidence reason
  4. 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-11-08 08:41:23.477639
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 12. 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
    js8713.com detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Blocklist Detection · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 10 of 10
  • Spamhaus DBL
    Spamhaus DBL recorded: spam domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 19
  • 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.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 9/92
  • Blocklist Detection
    Found in blocklists: OpenPhish
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • 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. AlienVault OTX

    3 community references

    View source
  2. Added to PhishDestroy

    js8713.com

    View source
  3. URLScan

    Malicious · engine verdict · score 19

    View source
  4. VirusTotal

    9/92 engine detections

    View source
  5. Wayback Machine

    Page archived

    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

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 9 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Open report OTX 3 refs 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?

4 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 js8713.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.

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/js8713.com"
  title="PhishDestroy threat report for js8713.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>