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@netim.net.
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.
absaaiinvest.digital returned HTTP status 200 on 2026-10-01, a dated response record. The domain was first observed on 2026-08-28, when its PageSpeed performance score was recorded as 87.
Recorded Evidence
The domain was registered with NETIM SAS on 2026-06-21, and an SSL certificate from ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2 was scanned on 2026-08-29. VirusTotal reported 19 detections across 89 scanners on 2026-09-12. OTX recorded 5 pulses on 2026-08-31, and the PhishDestroy internal listing was recorded as true.
Interpretation
The HTTP check, OTX, VirusTotal, and SSL scan carry different observation dates, so their records describe separate moments rather than one synchronized snapshot. Because the PhishDestroy listing and the first-observed date also fall on distinct dates, a reader can compare timing across sources without treating any single record as current.
Recommended Actions
Retain the dated records for absaaiinvest.digital, including the HTTP, SSL, OTX, and VirusTotal observations, so later checks can be compared against them. When new observations are collected, compare each against the corresponding dated source rather than combining them. Avoid submitting sensitive information to absaaiinvest.digital while any review remains open.
DOM Analysisanalyzed 2026年10月9日score 98/1001 brand signal
Submitted URLhttp://absaaiinvest.digital/
Favicon Hash
案件 ID
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.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-13 01:52:43 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 01:52:43 UTClast content: 2026-10-13 01:52:43 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.
技术 · 3 identified
J
jsDelivr
CDN
JSDelivr is a free public CDN for open-source projects. It can serve web files directly from the npm registry and GitHub repositories without any configuration.
Google PageSpeed Insights — mobile performance audit of absaaiinvest.digital· checked Aug 28, 2026
87
Needs Work
Performance
FCP
1.81s
First Contentful Paint
LCP
1.81s
Largest Contentful Paint
CLS
0.139
Cumulative Layout Shift
TBT
286ms
Total Blocking Time
SI
1.81s
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.
VirusTotal Detections Update2026-08-30 00:39:23 UTC
VirusTotal scanner detections updated from 19 to 18. Resolved alerts: ZeroFox.
VirusTotal Detections Update2026-08-29 03:00:54 UTC
VirusTotal Detections Update2026-08-29 00:22:47 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: SOCRadar.
Threat First Observed2026-08-28 19:36:48 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 185.62.57.40.
威胁响应 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.
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.
