Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 4. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
langxinhe.net favicon

langxinhe.net

In short

langxinhe.net is a phishing page detected by PhishDestroy on 2026-10-25.

“朗信和 — AI驱动的零佣金智能投资平台”

Registrar
Dynadot
Resolved IP
158.94.210.119
Registered
Oct 22, 2026
PhishDestroy assessment High
Availability Server error The latest stored response was inconclusive Observed HTTP probe
VirusTotal detections: 4/92 Spamhaus DBL: spam domain Young domain: 3 days old
VirusTotal
engine detections ·
OTX
community references
Cloudflare Radar
Page captures
open gallery
Domain age
Reports sent
No sent record
OTX: 3 refs Oct 26, 2026
X Telegram API

Analysis

Domain summary

langxinhe.net is a phishing page detected by PhishDestroy on 2026-10-25. Risk: high (65/100). Registrar: Dynadot. Status: Server error. Hosting: Omegatech LTD. VirusTotal: 4/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

High
VirusTotal
4 / 92
OTX
3 community refs
Page captures
4

PhishDestroy threat report

Overview

PhishDestroy added langxinhe.net to its internal blocklist on 2026-10-26 based on a trusted auto‑rule that flagged the site as unknown due to insufficient page content. The recorded page title reads "朗信和 — AI驱动的零佣金智能投资平台". The domain was first seen by PhishDestroy on 2026-10-26, four days after its registration on 2026-10-22.

How the scam works

While no specific malicious behavior was observed on the page, the combination of vendor detections and spam listings suggests the site could be used for typical phishing or scam tactics, such as presenting a legitimate‑looking service to lure users into providing credentials or personal information. Such schemes rely on deceptive branding and persuasive language to convince visitors to trust the site.

Evidence

VirusTotal flagged the domain as malicious on 2026-10-25, with 4 detections out of 92 engines labeling it phishing. Google Safe Browsing on 2026-10-26 did not flag the URL, while URLScan’s machine‑learning engine gave a malicious score of 99 on the same day, though its overall verdict was clean. Cloudflare Radar on 2026-10-26 reported phishing and several scam‑related risk tags, and Spamhaus DBL listed the domain as spam on that date. OTX showed three pulses referencing the domain, and PhishDestroy’s internal blocklist marks it as suspicious.

Infrastructure

The domain was registered with Dynadot Inc on 2026-10-22 and used Cloudflare name servers (guss.ns.cloudflare.com, jill.ns.cloudflare.com). The recorded IP was 158.94.210.119, associated with Omegatech LTD in the Netherlands. The TLS certificate, issued by Let’s Encrypt, was valid from 2026-10-25 to 2027-01-23.

What to do

Avoid entering any credentials, personal data, or financial information on langxinhe.net. If you have already submitted such data, change related passwords and monitor accounts for unauthorized activity. Security teams should block the domain at the network perimeter, review access logs for any connections to the recorded IP, and apply standard phishing mitigation policies.

Source evidenceVirusTotal 4 / 92 · OTX 3 references 8 sources

VirusTotal

4 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
54
Malicious
4
Suspicious
0
Undetected
34

Vendor labels

CRDF
malicious
SOCRadar
phishing
Gridinsoft
phishing
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

Dynadot Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    hostmaster.langxinhe.net
    Value
    ns1.dyna-ns.net
  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.dyna-ns.net
  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.dyna-ns.net
  • TTL, seconds
    300
    Type
    A
    Value
    158.94.210.119

DNS records observed

JARM fingerprint

40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319

Certificate

Subject alternative names
  • langxinhe.net
Issuer
Let's Encrypt / YE2
Serial
53fc407a6e16f0cadb5da2d27db0b21504d
SHA-256
d358a7a90e1996da0f3611157ce6c067ae5bf548ba85fcbdc14c16cde52cc20d
Subject
langxinhe.net
Valid until
Valid from

Registration record

Registrar
Dynadot Inc
Registrar IANA ID
472
Registrar URL
http://www.dynadot.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • guss.ns.cloudflare.com
  • jill.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 54,
    "malicious": 4,
    "suspicious": 0,
    "undetected": 34
}
Vendor labels
{
    "CRDF": "malicious",
    "SOCRadar": "phishing",
    "Gridinsoft": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
Dynadot Inc
Created
2026-10-22T15:04:26Z
Expires
2027-10-22T15:04:26Z
Updated
2026-10-22T15:04:39Z
First seen
2026-10-22T16:38:31Z
DNS records
[
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.langxinhe.net",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "158.94.210.119"
    }
]
Dns at
2026-10-25T16:58:38Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "langxinhe.net"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "53fc407a6e16f0cadb5da2d27db0b21504d",
    "sha256": "d358a7a90e1996da0f3611157ce6c067ae5bf548ba85fcbdc14c16cde52cc20d",
    "subject": "langxinhe.net",
    "valid_to": "2027-01-23T15:46:38Z",
    "valid_from": "2026-10-25T15:46:39Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-10-22T15:04:26Z",
    "updated": "2026-10-22T15:04:39Z",
    "expires": "2027-10-22T15:04:26Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "guss.ns.cloudflare.com",
        "jill.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-22T15:04:26Z",
        "last changed": "2026-10-22T15:04:39Z",
        "registration": "2026-10-22T15:04:26Z",
        "registrar expiration": "2027-10-22T15:04:26Z",
        "last update of RDAP database": "2026-10-22T15:13:17Z"
    }
}
Separate source record · 4 malicious + 0 suspicious / 92 · 2026-10-25 16:53:21 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-25T16:53:21Z
fetched_at
2026-10-25T23:52:05Z
stats
{"timeout":0,"harmless":54,"malicious":4,"suspicious":0,"undetected":34}

Cloudflare Radar

Scam

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

596cb334-73ab-416c-887b-fe681e159934

Final URL

https://langxinhe.net/

HTTP response

200

Navigation history

  • URL
    https://langxinhe.net/
    Status
    200

DOM structure hash

4be30671e8e447c958fe3c2e8232e62a2dc2302da72aac69463ae49e6ab78841

Document hash

c6d6506ba32f6841a01211a96bc10a06a4cfe8b918f4bcbb013ff0e70cb555f3

Phishing classifier result

  • phishing

URL risk categories

  • Scam

Domain risk categories

  • Scam
  • Security threats
  • Newly Seen Domains
  • Security Risks
  • New Domains
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    langxinhe.net
    Type
    A
    Value
    158.94.210.119

DNSSEC valid

No

IP address

158.94.210.119

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Nameservers
  • guss.ns.cloudflare.com
  • jill.ns.cloudflare.com
Original source fields · JSON
Uuid
596cb334-73ab-416c-887b-fe681e159934
Final url
https://langxinhe.net/
Status
200
History
[
    {
        "url": "https://langxinhe.net/",
        "status": 200
    }
]
DOM structure hash
4be30671e8e447c958fe3c2e8232e62a2dc2302da72aac69463ae49e6ab78841
Document hash
c6d6506ba32f6841a01211a96bc10a06a4cfe8b918f4bcbb013ff0e70cb555f3
Phishing v2
[
    "phishing"
]
Url risks
[
    "Scam"
]
Domain risks
[
    "Scam",
    "Security threats",
    "Newly Seen Domains",
    "Security Risks",
    "New Domains",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "langxinhe.net",
        "type": "A",
        "value": "158.94.210.119"
    }
]
Dnssec valid
false
Ip
158.94.210.119
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-10-22T15:04:26Z",
    "updated": "2026-10-22T15:04:39Z",
    "expires": "2027-10-22T15:04:26Z",
    "nameservers": [
        "guss.ns.cloudflare.com",
        "jill.ns.cloudflare.com"
    ]
}
Separate stored summary: suspicious · 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
suspicious
categories
["Scam","Security Risks","New Domains","Security threats"]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

Spamhaus DBL

spam domain

URLScan

Malicious · engine verdict · score 99

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a1755d-dc69-75f5-a959-2959dbabb3ab

Final URL

https://langxinhe.net/

HTTP response

200

Redirect type

sub-domain

Redirects

  • To
    https://www.langxinhe.net/
    From
    http://www.langxinhe.net/
    Status
    307
  • To
    http://www.langxinhe.net/
    From
    https://www.langxinhe.net/
    Status
    307
  • To
    https://langxinhe.net/
    From
    http://www.langxinhe.net/
    Status
    301

IP address

158.94.210.119

Contacted domains

  • www.langxinhe.net

Contacted IP addresses

  • 158.94.210.119

Autonomous systems (ASN)

  • 202412

Server countries

  • NL

Document hash

5b67f36edf3b2031b4b84e0a9a75bb401b7492a31dd1ce0d2f01f266d1dbeda6

Script hashes

  • 8aa5f8f647356dcd4fc5dbbe0efd5bc0e8da74026bc61e24636e2e1f5749b0ce

JavaScript globals

  • __dclq
  • __dclOrig
  • __dclFlush
  • __smsCheckBeforeSubmit
  • __isSmsEnabled
  • __isSmsVerified
  • intlTelInput

Cookies

  • connect.sid

TLS session and certificate

Subject alternative names
  • langxinhe.net
Cipher
AES_128_GCM
Issuer
YE2
Subject
langxinhe.net
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Registered domain age, days

0

Certificate age, days

0

Certificate validity, days

89

Page requests

7

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
99
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Content-type
text/html; charset=utf-8
X-content-type-options
nosniff
Referrer-policy
same-origin
Original source fields · JSON
Uuid
01a1755d-dc69-75f5-a959-2959dbabb3ab
Final url
https://langxinhe.net/
Status
200
Redirected
sub-domain
Redirects
[
    {
        "to": "https://www.langxinhe.net/",
        "from": "http://www.langxinhe.net/",
        "status": 307
    },
    {
        "to": "http://www.langxinhe.net/",
        "from": "https://www.langxinhe.net/",
        "status": 307
    },
    {
        "to": "https://langxinhe.net/",
        "from": "http://www.langxinhe.net/",
        "status": 301
    }
]
Ip
158.94.210.119
Contacted domains
[
    "www.langxinhe.net"
]
Contacted IP addresses
[
    "158.94.210.119"
]
Asns
[
    "202412"
]
Countries
[
    "NL"
]
Document hash
5b67f36edf3b2031b4b84e0a9a75bb401b7492a31dd1ce0d2f01f266d1dbeda6
Script hashes
[
    "8aa5f8f647356dcd4fc5dbbe0efd5bc0e8da74026bc61e24636e2e1f5749b0ce"
]
Globals
[
    "__dclq",
    "__dclOrig",
    "__dclFlush",
    "__smsCheckBeforeSubmit",
    "__isSmsEnabled",
    "__isSmsVerified",
    "intlTelInput"
]
Cookies
[
    "connect.sid"
]
Tls
{
    "san": [
        "langxinhe.net"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "langxinhe.net",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-23T15:46:38Z",
    "valid_from": "2026-10-25T15:46:39Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
89
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "x-content-type-options": "nosniff",
    "referrer-policy": "same-origin"
}
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
01a1755d-dc69-75f5-a959-2959dbabb3ab
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

0 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-25T23:57:23Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-10-25T23:57:23Z
source_timestamp
2026-10-26 00:57:23
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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
langxinhe.net — Suspicious Domain
ai_description
PhishDestroy flags langxinhe.net as a suspicious domain after first detection on 2026-10-26, noting multiple vendor detections and a Spamhaus spam listing.
ai_generated_at
2026-10-25T23:53:08Z
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: 19 fields

Mail configuration

SPF lookups
0

CAA records

Domain
langxinhe.net

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Sitemap

Present
Yes
URL count
5

Ports

Open ports
  • 22
  • 80
  • 443

Carbon estimate

Bytes
75931
CO₂, grams
0.0028
Cleaner than, %
28

DNS servers

Nameservers
  • IP address
    162.159.26.92
    Host
    ns1.dyna-ns.net
  • IP address
    162.159.24.5
    Host
    ns2.dyna-ns.net
DNS zone
langxinhe.net

Cookies

Cookies
  • Name
    cf-c
    HTTP-only
    Yes
    SameSite
    Lax
  • Name
    __cf_clicked
  • Name
    ph_phc_t6w4wzJE2sbz4ro8LmZZTssm5go3KD6mP7QsqcDQRSp6_posthog
    Secure
    Yes
    SameSite
    Lax

Location

IP address
158.94.210.119
ASN
202412
Organization
Omegatech LTD
City
Amsterdam
Country
NL

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
langxinhe.net

DNS records

A
  • 158.94.210.119
NS
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net
SOA
Primary nameserver
guss.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418432770
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

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
same-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
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
158.94.210.119
IP version
4

Redirects

Redirect chain
  • https://langxinhe.net

Page links

Internal links
8

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

HTTP headers

Response headers
Content-type
text/html; charset=utf-8
X-content-type-options
nosniff
Referrer-policy
same-origin
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "langxinhe.net"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Sitemap
{
    "present": true,
    "url_count": 5
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 75931,
    "co2_grams": 0.0028,
    "cleaner_than": 28
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.26.92",
            "host": "ns1.dyna-ns.net"
        },
        {
            "ip": "162.159.24.5",
            "host": "ns2.dyna-ns.net"
        }
    ],
    "zone": "langxinhe.net"
}
Cookies
{
    "cookies": [
        {
            "name": "cf-c",
            "http_only": true,
            "same_site": "Lax"
        },
        {
            "name": "__cf_clicked"
        },
        {
            "name": "ph_phc_t6w4wzJE2sbz4ro8LmZZTssm5go3KD6mP7QsqcDQRSp6_posthog",
            "secure": true,
            "same_site": "Lax"
        }
    ]
}
Location
{
    "ip": "158.94.210.119",
    "asn": "202412",
    "org": "Omegatech LTD",
    "city": "Amsterdam",
    "country": "NL"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "langxinhe.net"
}
DNS records
{
    "A": [
        "158.94.210.119"
    ],
    "NS": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ],
    "SOA": "{\"nsname\": \"guss.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418432770, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "same-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "158.94.210.119",
    "family": 4
}
Redirects
{
    "chain": [
        "https://langxinhe.net"
    ]
}
Page links
{
    "internal_count": 8
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-10-22T15:04:26Z",
    "updated": "2026-10-25T15:44:15Z",
    "expires": "2027-10-22T15:04:26Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "x-content-type-options": "nosniff",
        "referrer-policy": "same-origin"
    }
}

Questions about langxinhe.net

Is langxinhe.net legit?

No. PhishDestroy classifies langxinhe.net as a phishing page (risk: high, 65/100); it was first detected on 2026-10-25. VirusTotal: 4/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is langxinhe.net safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on langxinhe.net. 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 langxinhe.net?

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 matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 4 captures

All capture links and hashes (4)

Domain details

Domain
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
Hosting abuse contact abuse@omegatech.sc Omegatech LTD · AS202412
RegistrationCreated Oct 22, 2026 (3d · Brand New!) — Expires Oct 22, 2027
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 0/100
Submitted URLhttp://www.langxinhe.net/
Favicon Hash
Observed page title
朗信和 — AI驱动的零佣金智能投资平台
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 89 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
158.94.210.119
Network ASN
AS202412
Organization
Omegatech LTD
Observed location
Amsterdam, NL

Nameservers 2

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

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-25 15:46:39
Valid until
2027-01-23 15:46:38
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintd358a7a90e1996da0f3611157ce6c067ae5bf548ba85fcbdc14c16cde52cc20d
Certificate names · 1 SAN
  • langxinhe.net

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

Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 4 detections
alphaMountain.ai
CRDF
Gridinsoft
SOCRadar

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of langxinhe.net · checked Oct 26, 2026

100
Good
Performance
FCP
0.97 s
First Contentful Paint
LCP
1.5 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
2.28 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://www.langxinhe.net/
Final URL: https://langxinhe.net/
Response
HTTP 200
HTML body
831 B
Compressed
431 B
Links
0 internal · 0 external
Selected response headers
Cache-Control: no-cache, no-store, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
X-Powered-By: Express
Security headers present
X-Content-Type-OptionsReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 11
Alt-Svc
h3=":443"; ma=2592000
Cache-Control
no-cache, no-store, must-revalidate
Content-Encoding
gzip
Content-Length
436
Content-Type
text/html; charset=utf-8
Date
Sun, 25 Oct 2026 23:20:17 GMT
Referrer-Policy
same-origin
Vary
Accept-Encoding
Via
1.1 Caddy
X-Content-Type-Options
nosniff
X-Powered-By
Express

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

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.

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. Domain monitor · First collection record

    Reachable

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
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    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-10-26 00:22:39.000000
    Evidence SHA-256
    ecb38c04e191ac59c409676aa17cbef805cd0feb3a3a57ffbad7d24a6f4d7dd9
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 00:22:39
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    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-10-26 00:22:39.000000
    Evidence SHA-256
    ecb38c04e191ac59c409676aa17cbef805cd0feb3a3a57ffbad7d24a6f4d7dd9
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 00:22:39
    Evidence reason

Recorded activity

6 entries
  1. AlienVault OTX

    3 community references

    View source
  2. VirusTotal

    4/92 engine detections

    View source
  3. URLScan

    Page captured

    View source
  4. Cloudflare Radar

    Scam

    View source
  5. Wayback Machine

    Page archived

    View source
  6. Added to PhishDestroy

    langxinhe.net

    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.

Check for cloaking

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

langxinhe.net

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Server error
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.

Official reporting routes

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 langxinhe.net)
  • 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

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.

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