xpr-bitget.com.cn was observed on 2026-10-09 with a VirusTotal check recording 1 detection out of 92 scanners, providing a measurable security indicator for this domain. The domain is also referenced on multiple external blocklists, expanding its recorded security profile.
Recorded Evidence
On 2026-10-09, xpr-bitget.com.cn was listed on both the MetaMask and SEAL external blocklists. VirusTotal checked the domain on the same date, recording 1 detection out of 92 total scanners. OTX pulses included the domain on 2026-10-09, and PhishDestroy listed it internally on that date. The PageSpeed performance score was measured at 100 on 2026-10-09.
Interpretation
The VirusTotal record contains a quantitative detection result, documenting how xpr-bitget.com.cn was assessed by numerous security scanners. OTX and PhishDestroy each provide additional intelligence, with OTX recording pulse activity and PhishDestroy maintaining an internal listing. The presence on both MetaMask and SEAL blocklists broadens the context for understanding the domain's recorded security observations.
Recommended Actions
Preserve all records for xpr-bitget.com.cn from MetaMask, SEAL, VirusTotal, OTX, and PhishDestroy for ongoing reference. Compare these source records over time to monitor for changes in blocklist status or detection counts. Use the PageSpeed performance score as a technical benchmark when evaluating future infrastructure or performance adjustments.
DOM Analysisanalyzed 2026年10月9日score 83/1002 brand signals
Submitted URLhttp://xpr-bitget.com.cn/
Favicon Hash
ページタイトル
查理用她的阴户说服她的教练
Impersonates
GmailGoogle
TLS証明書
Hostname coverage not recorded·
発行者 YR2
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
142.4.109.104
Network ASN
AS54600
Organization
PEG TECH INC
Observed location
San Jose, US
Server header
nginx
ネームサーバー 4
a.share-dns.com
a3.share-dns.com
b.share-dns.net
b3.share-dns.net
Location describes the IP network.
TLS証明書
Issuer
YR2
Hostname coverage
Hostname coverage not recorded
Collection time
2026-10-09 19:02:09 UTC
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: StaleRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 02:17:38 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 02:17:38 UTClast content: 2026-10-11 02:17:38 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.
使用技術 · 3 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Last analyzed Previous stored snapshot: 1 detection
CRDF
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of xpr-bitget.com.cn· checked Oct 9, 2026
100
Good
Performance
FCP
0.9s
First Contentful Paint
LCP
1.5s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.54s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-09 15:47:26 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 142.4.109.104.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
(MY)
