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.
allcityhub.shop returned HTTP status 301 on 2026-10-01, according to the recorded HTTP check. The domain was first observed on 2026-09-26 and appears in the PhishDestroy internal listing.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 301 for allcityhub.shop. VirusTotal, checked on 2026-09-29, reported 6 detections across 91 scanners. OTX, checked on 2026-09-29, listed 4 pulses. The domain was first observed on 2026-09-26, and the PhishDestroy internal listing was recorded as true. Registration occurred on 2026-06-13 with registrar Dynadot Inc., while the SSL certificate, scanned on 2026-09-26, was issued by Let's Encrypt / YE2.
Interpretation
The recorded HTTP status describes only the response captured on its check date, while the VirusTotal and OTX figures reflect separate checks on their own dates. The PhishDestroy internal listing and the first-observation date provide additional chronological markers. Because these sources were recorded on different dates, their outputs should be read as independent observations rather than a single combined measurement.
Recommended Actions
For allcityhub.shop, preserve the HTTP check record, the VirusTotal result, and the OTX result as separate source records. Compare the PhishDestroy internal listing against later observations of the same catalogue. Re-check the HTTP response and the VirusTotal and OTX entries on a recurring schedule, and retain each dated output for comparison.
DOM Analysisanalyzed 2026年10月9日score 88/1004 brand signals
Submitted URLhttp://allcityhub.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:12:15 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:12:15 UTClast content: 2026-10-11 10:12:15 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 allcityhub.shop· checked Sep 26, 2026
76
Needs Work
Performance
FCP
3s
First Contentful Paint
LCP
3.42s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
59ms
Total Blocking Time
SI
15.71s
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 21:14:10 UTC
VirusTotal scanner detections updated from 5 to 6. Added scanner alerts: Forcepoint ThreatSeeker.
VirusTotal Detections Update2026-09-26 19:41:03 UTC
VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-26 15:34:19 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 91.246.50.210.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
14 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.
