On 2026-10-01, foundraehq.shop was listed in the PhishDestroy internal catalogue, indicating a recorded observation by that source. The domain was first observed on 2026-09-03, providing a reference point for subsequent checks.
Recorded Evidence
VirusTotal checked foundraehq.shop on 2026-09-14 and recorded 12 detections out of 89 scanners. OTX recorded 4 pulses for this domain on 2026-09-14. The SSL certificate was issued by Let's Encrypt / YE1 and scanned on 2026-09-14. The registrar for foundraehq.shop is Dynadot Inc.
Interpretation
These source observations from PhishDestroy, VirusTotal, and OTX each reflect their own data collection methods and timeframes. The first-observed date gives context for the timing of these checks, but does not indicate any change in status between observations. Registration and SSL certificate details provide additional reference points for the domain's technical setup.
Recommended Actions
For foundraehq.shop, retain the PhishDestroy listing and VirusTotal detection records as separate reference points for future review. Compare the OTX pulse record to the PhishDestroy listing for ongoing monitoring. Keep the SSL certificate and registration details available for technical verification in subsequent checks.
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-11 10:41:32 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-20 10:15:01 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.
使用技術 · 1 identified
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Last analyzed First positive detection Previous stored snapshot: 12 detections
alphaMountain.ai
BitDefender
CRDF
ESET
G-Data
Gridinsoft
LevelBlue
Lionic
ネットクラフト
PhishFort
SOCRadar
Webroot
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of foundraehq.shop· checked Sep 14, 2026
64
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
4.45s
Largest Contentful Paint
CLS
0.03
Cumulative Layout Shift
TBT
474ms
Total Blocking Time
SI
4.92s
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-09-14 11:23:12 UTC
Domain ingestion complete. Initial state is marked as alive.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
6 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
脅威の検知
foundraehq.shop 検出され、詳細な分析のためにキューに入れられた
2026年9月3日
Cloudflare Radar Report
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)
