ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@forticore.digital.
The latest stored availability evidence still shows the domain reachable; 9 days 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.
On 2026-10-01 fortvoz.com appeared in the PhishDestroy internal catalogue, and PageSpeed recorded a performance score of 76 for the domain on the same date. The domain’s registration occurred on 2026-08-28 with PDR Ltd. d/b/a PublicDomainRegistry.com.
Recorded Evidence
fortvoz.com was first observed on 2026-10-01. VirusTotal examined the domain on 2026-09-25 and reported 5 detections out of 91 total scanners. OTX recorded 1 pulse for fortvoz.com on 2026-10-01. PageSpeed measured a performance score of 76 on 2026-10-01.
Interpretation
The PhishDestroy internal catalogue entry indicates the domain has been flagged for review. VirusTotal’s detections and OTX’s pulse provide additional technical observations for comparison. PageSpeed’s score reflects a moderate level of front-end performance on the date measured.
Recommended Actions
Preserve the PhishDestroy listing and VirusTotal detection record for fortvoz.com. Compare the PageSpeed performance score against future measurements to track any changes. Use these dated records as reference points for ongoing monitoring decisions.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 10:37:16 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:37:16 UTClast content: 2026-10-11 10:37:16 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.
Google PageSpeed Insights — mobile performance audit of fortvoz.com· checked Oct 1, 2026
76
Needs Work
Performance
FCP
4.19s
First Contentful Paint
LCP
4.23s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
14ms
Total Blocking Time
SI
4.19s
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-01 17:27:11 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 46.29.26.38.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
12 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.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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.
PDF notice generated Notice text archived (594 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (DE):
German Criminal Code § 263 (Fraud)
German Criminal Code § 263a (Computer Fraud)
Telemedia Act (TMG)
German law prohibits fraud and computer-based deception.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
(DE)
