Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
canardd.com returned HTTP status 502 on 2026-10-01, according to the recorded HTTP check. The same record set shows an initial observation date of 2026-09-11, when several other source checks were also captured.
Recorded Evidence
The registration date recorded for canardd.com is 2026-07-23, with NameSilo, LLC listed as registrar. On 2026-09-11, VirusTotal recorded 19 detections across 89 scanners, and OTX recorded 1 pulse. The PhishDestroy internal listing was also recorded as true, while the SSL scan on 2026-09-11 identified Let's Encrypt / YE1 as issuer.
Interpretation
The HTTP check on 2026-10-01 and the VirusTotal, OTX, and SSL observations from 2026-09-11 come from different dates, so they describe separate snapshots rather than one continuous state. Because the PhishDestroy listing and the OTX pulse were recorded on 2026-09-11, while the HTTP response was captured later, a reader should compare them as dated records rather than as a single verdict.
Recommended Actions
Anyone reviewing canardd.com should retain the dated source records, including the 2026-10-01 HTTP result and the 2026-09-11 VirusTotal, OTX, and SSL observations, so later checks can be compared against them. Subsequent observations of canardd.com should be logged with their own dates before any conclusion is drawn. During review, avoid submitting sensitive information to canardd.com or relying on a single dated response as a current description.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='canardd.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 01:14:27 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-11 23:01:46 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-11 23:01:46 UTC → 2026-09-30 16:14:55 UTC · 449.22hmidpoint estimate ≈ 2026-09-21 07:38:20 UTC · precision low · basis bounded
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.
Google PageSpeed Insights — mobile performance audit of canardd.com· checked Sep 11, 2026
100
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
0.77s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.96s
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.
Domain Status Transition2026-09-12 11:00:48 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-11 03:39:19 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 43.165.7.184.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
15 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)
PhishDestroy Investigation
