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@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 15 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.
alfamedonlinehealth.shop was recorded returning an HTTP 301 status on 2026-10-01, a redirect response captured during an HTTP check. The same domain was first observed on 2026-09-26, and its PageSpeed performance score was recorded as 85 on that date.
Recorded Evidence
VirusTotal recorded 9 detections across 91 scanners for alfamedonlinehealth.shop on 2026-09-29. OTX listed 4 pulses for the domain on 2026-09-29. The PhishDestroy internal listing was recorded as true, and the domain was first observed on 2026-09-26. Registration was recorded with Dynadot Inc. on 2026-05-20. The HTTP check returned a 301 status on 2026-10-01, and the PageSpeed performance score was 85 on 2026-09-26.
Interpretation
The VirusTotal, OTX, and PhishDestroy records each describe separate observations of alfamedonlinehealth.shop, and the HTTP and PageSpeed entries document technical responses recorded on different dates. Because these sources measure different things, their values should be read individually rather than combined. The registration and first-observation dates place the domain's recorded timeline within 2026 without indicating any particular activity.
Recommended Actions
For alfamedonlinehealth.shop, preserve the VirusTotal, OTX, and PhishDestroy records so future checks can be compared against them. Keep the HTTP response and PageSpeed performance score as separate technical observations. When reviewing alfamedonlinehealth.shop again, compare each source's new output to its earlier record and treat the domain as the unit of review.
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 observationRedirectingHTTP redirect observed80%2026-10-11 10:12:55 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:12:55 UTClast content: 2026-10-11 01:46:50 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.
Google PageSpeed Insights — mobile performance audit of alfamedonlinehealth.shop· checked Sep 26, 2026
85
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
2.89s
Largest Contentful Paint
CLS
0.008
Cumulative Layout Shift
TBT
238ms
Total Blocking Time
SI
3.6s
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-09-28 15:10:44 UTC
VirusTotal scanner detections updated from 8 to 9. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-26 17:01:49 UTC
VirusTotal scanner detections updated from 7 to 8. Added scanner alerts: BitDefender, G-Data. Resolved alerts: SOCRadar.
VirusTotal Detections Update2026-09-26 09:41:30 UTC
VirusTotal scanner detections updated from 6 to 7. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-26 01:27:06 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 23.252.79.162.
威胁响应 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.
