The domain au-tiktok-vs.com was recorded with a VirusTotal detection entry on 2026-10-11, documenting analysis results from a large set of security scanners. This domain was first observed on 2026-10-11, providing a recent reference point for its activity timeline.
Recorded Evidence
VirusTotal checked au-tiktok-vs.com on 2026-10-11 and recorded 20 detections out of 92 total scanners. OTX included the domain in 4 pulses as of 2026-10-12. The PhishDestroy internal listing also contains an entry for this domain, and its registration date is recorded as 2026-09-09 through Amazon Registrar, Inc. PageSpeed measured a performance score of 100 on 2026-10-12.
Interpretation
VirusTotal documents how many security engines flagged au-tiktok-vs.com, offering a quantitative measurement of security scanner outcomes. OTX records the domain’s inclusion in several intelligence pulses, which tracks its presence in external security datasets. The PhishDestroy internal listing adds another layer of recorded evidence, supporting a multi-source review of the domain’s profile.
Recommended Actions
For au-tiktok-vs.com, retain all VirusTotal, OTX, and PhishDestroy records to support future reference and comparison. Use the VirusTotal detection and OTX pulse records as benchmarks for ongoing monitoring and to track any changes in scanner or intelligence outcomes.
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.
Last analyzed First positive detection Previous stored snapshot: 20 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
Ermes
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
Fortra
G-Data
Gridinsoft
卡巴斯基
Lionic
MalwareURL
Netcraft
OpenPhish
SOCRadar
Sophos
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of au-tiktok-vs.com· checked Oct 12, 2026
100
Good
Performance
FCP
0.79s
First Contentful Paint
LCP
0.79s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.57s
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-12 10:14:16 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 47.86.105.213.
威胁响应 Pipeline
发现
Analysis
Monitoring
8 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.
