bondtracks.com
“Bond Secure Tracking Solutions LLC | GPS Ankle Monitoring in Wake County, NC”
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@v-sys.org.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Evidence Summary
Assessment
Stored evidence for bondtracks.com: VirusTotal recorded 3 detections among 91 scanners on 2026-08-15. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for bondtracks.com. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 3 detections among 91 scanners in the stored snapshot dated 2026-08-15. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-08-15 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
MetaMask and SEAL are recorded as named external blocklist observations for bondtracks.com in the snapshot dated 2026-08-15. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains bondtracks.com as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed bondtracks.com on 2026-08-14. The MetaMask and SEAL blocklist snapshot is dated 2026-08-15 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-07-14. A URLScan reference was stored on 2026-08-14 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
The source stores 185.66.90.243 as the observed address in this record. The registration date for bondtracks.com is recorded as 2026-07-14. The stored ASN observation records AS30860 and YURTEH-AS Virtual Systems LLC, UA in this record. The observed server header is recorded as nginx in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The bondtracks.com record states that VirusTotal recorded 3 detections among 91 scanners on 2026-08-15. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-08-15. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 185.66.90.243. The supported conclusion is bounded to the exact stored observations for bondtracks.com. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to bondtracks.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain bondtracks.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to bondtracks.com. The stored record does not justify extending that rule to 185.66.90.243 or to other infrastructure records.
Forensic History & Detection Timeline
-
Domain Status Transition Aug 26, 2026 · 00:15 UTCDomain state transitioned from dead to alive.
-
Domain Status Transition Aug 26, 2026 · 00:00 UTCDomain state transitioned from alive to dead.
-
VirusTotal Detections Update Aug 15, 2026 · 01:44 UTCVirusTotal scanner detections updated from 0 to 3. Added scanner alerts: Forcepoint ThreatSeeker, Gridinsoft, SOCRadar.
-
Threat First Observed Aug 14, 2026 · 06:48 UTCDomain ingestion complete. Initial state is marked as alive pointing to IP
185.66.90.243.
Threat Response Pipeline
Public Blocklist Status
Stored Capture · 4 sources
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT
Accreditation and RAA context
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Technologies · 1 identified
VirusTotal Analysis
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of bondtracks.com · checked Aug 14, 2026
Evidence & External Reports
PD-20260814-40A0F6 Recipient: abuse@v-sys.org Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive