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; 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.
abovethecloudslabel.shop returned HTTP status 200 in a check recorded on 2026-10-01, one of several dated observations collected for this domain. The same domain was first observed on 2026-09-09, according to the recorded first observation value.
Recorded Evidence
A VirusTotal scan dated 2026-09-18 recorded 15 detections across 89 scanners. OTX recorded 4 pulses on 2026-09-10. The domain appears in the PhishDestroy internal listing, and its registration date is 2026-07-23 with registrar Dynadot Inc. An SSL scan dated 2026-09-09 identified the issuer as Let's Encrypt / YE1. The HTTP check on 2026-10-01 returned status 200, and the PageSpeed check on 2026-09-09 produced a performance score of 69.
Interpretation
The VirusTotal and OTX records describe scanner and pulse observations on their own dates, while the PhishDestroy listing reflects a publisher catalogue entry. The HTTP response and PageSpeed score describe only what those checks recorded, not all content or behavior on the domain. The dates span from 2026-07-23 to 2026-10-01, allowing a reader to compare observations across that window without treating any single record as a verdict.
Recommended Actions
For abovethecloudslabel.shop, preserve the VirusTotal and OTX records as separate source documents for later comparison. Retain the PhishDestroy listing entry and the HTTP check result as distinct records, since each captures a different kind of observation. Compare future scans against these saved records rather than relying on any single measurement.
DOM Analysisanalyzed 2026年9月9日score 98/1001 brand signal
Submitted URLhttp://abovethecloudslabel.shop/
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-11 10:07:25 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:07:25 UTClast content: 2026-10-11 10:07:25 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 abovethecloudslabel.shop· checked Sep 9, 2026
69
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
9.23s
Largest Contentful Paint
CLS
0.011
Cumulative Layout Shift
TBT
141ms
Total Blocking Time
SI
2.89s
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-10-09 01:45:01 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-24 22:07:31 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-09 15:36:52 UTC
VirusTotal scanner detections updated from 7 to 8. Added scanner alerts: Gridinsoft.
VirusTotal Detections Update2026-09-09 12:24:57 UTC
VirusTotal scanner detections updated from 6 to 7. Added scanner alerts: CRDF.
VirusTotal Detections Update2026-09-09 07:35:09 UTC
VirusTotal scanner detections updated from 5 to 6. Added scanner alerts: alphaMountain.ai.
VirusTotal Detections Update2026-09-09 04:55:26 UTC
VirusTotal scanner detections updated from 0 to 5. Added scanner alerts: Forcepoint ThreatSeeker, Kaspersky, LevelBlue, Netcraft, SOCRadar.
Threat First Observed2026-09-09 03:20:40 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 185.252.210.11.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
18 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.
