The domain teamledger.online was recorded with a PhishDestroy internal listing on 2026-10-13, alongside a PageSpeed performance score of 53 from the same date. This assessment also notes the presence of multiple external intelligence checks within the recorded timeline.
Recorded Evidence
PhishDestroy internally listed teamledger.online on 2026-10-13. OTX checked the domain on 2026-10-13, documenting three pulses. VirusTotal scanned the domain on 2026-09-30 and reported one detection out of 92 total scanners. The domain was registered with Global Domain Group LLC on 2026-09-23. PageSpeed measured a performance score of 53 on 2026-10-13.
Interpretation
PhishDestroy provides an internal listing record, which documents the domain's inclusion in its catalogue as of 2026-10-13. VirusTotal records a detection count and total scanner coverage, offering a technical snapshot of how the domain was evaluated by multiple security engines. The OTX pulses represent external intelligence entries, adding context to the domain's observed activity. These sources collectively capture a range of technical and intelligence-based measurements within a short timeline.
Recommended Actions
For teamledger.online, preserve the PhishDestroy internal listing and VirusTotal detection record for ongoing comparison. Retain OTX pulse entries and PageSpeed performance results as reference points for future checks. Use these documented records to inform any subsequent security reviews or technical assessments of the domain.
注册信息创建 2026年9月23日 (20d · Very New!)—Expires 2027年9月23日
技术详情Provenance & timestamps
首次发现2026年10月13日
Submitted URLhttps://teamledger.online/
Favicon Hash
ICANN OVERSIGHT
认证和 RAA 背景
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 11:57:10 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 11:57:10 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.
HSTS: observedDNSSEC: not observedWAF / firewall: observedCloaking flag: not observed
Open Graph title:Team Ledger | Live Dashboard
Open Graph description:Multi-team financial ledger with live results dashboard
Twitter card:summary_large_image
Saved response-header values · 16
Cache-Control
no-cache, no-store, must-revalidate
CF-Ray
a49e2c2ca912440d-EWR
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Tue, 13 Oct 2026 11:58:27 GMT
Expires
0
Last-Modified
Tue, 22 Sep 2026 10:32:42 GMT
Pragma
no-cache
Server
cloudflare
Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
Transfer-Encoding
chunked
x-cloud-trace-context
a1bec0ae1656519b8357a0ecd5d7f76c
X-Content-Type-Options
nosniff
x-manus-proxy-mode
transparent/1
x-powered-by
Express
Values retained by the collector; long values may be shortened during collection.
Crawler & disclosure files
Site configuration evidence
3 recorded files
Files, paths and sitemap entries retained by the collector.
robots.txt
Reachable (legacy)/robots.txt
HTTP response
200
Observed at
2026-10-13 13:58:29 UTC
来源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
Sitemap
Reachable (legacy)/sitemap.xml
HTTP response
200
Observed at
2026-10-13 13:58:29 UTC
来源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
security.txt
Reachable (legacy)/.well-known/security.txt
HTTP response
200
Observed at
2026-10-13 13:58:29 UTC
来源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
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-13 11:57:10 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.18.26.246.
威胁响应 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.
(US)
