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.
allcitynetworkofficial.shop returned an HTTP 301 response when checked on 2026-10-01, according to the recorded HTTP observation. The same domain was first observed on 2026-09-26, and its registration date is recorded as 2026-05-03.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 301 for allcitynetworkofficial.shop, while the first observation of the domain is dated 2026-09-26. VirusTotal, checked on 2026-09-29, reported 12 detections across 91 scanners, and OTX, also checked on 2026-09-29, listed 4 pulses. The domain appears in the PhishDestroy internal listing, and its registration date is recorded as 2026-05-03 with Dynadot Inc. as registrar. The SSL scan on 2026-09-26 identified Let's Encrypt / YE2 as the issuer, and PageSpeed on the same date returned a performance score of 78.
Interpretation
The HTTP record shows only the response observed on its check date, so it does not describe content or availability at other times. The VirusTotal and OTX results come from separate sources with their own collection methods, so their figures should be read individually rather than combined. The first observation and the HTTP check fall on different dates, which allows a reader to order the records but not to conclude that anything changed between them.
Recommended Actions
Preserve the HTTP response record for allcitynetworkofficial.shop and the first-observation entry as separate dated artifacts. Keep the VirusTotal and OTX results alongside them so each source can be compared on its own terms. Review the PhishDestroy internal listing entry and the PageSpeed record separately, and compare future checks against these saved observations.
DOM Analysisanalyzed 2026年10月9日score 98/1001 brand signal
Submitted URLhttp://allcitynetworkofficial.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:19 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:12:19 UTClast content: 2026-10-11 10:12:19 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 allcitynetworkofficial.shop· checked Sep 26, 2026
78
Needs Work
Performance
FCP
2.9s
First Contentful Paint
LCP
4.22s
Largest Contentful Paint
CLS
0.009
Cumulative Layout Shift
TBT
192ms
Total Blocking Time
SI
3.17s
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 23:18:01 UTC
VirusTotal scanner detections updated from 10 to 12. Added scanner alerts: Forcepoint ThreatSeeker, SOCRadar, VIPRE. Resolved alerts: LevelBlue.
VirusTotal Detections Update2026-09-28 15:28:26 UTC
VirusTotal scanner detections updated from 10 to 10. Added scanner alerts: Fortinet. Resolved alerts: SOCRadar.
VirusTotal Detections Update2026-09-27 00:54:24 UTC
VirusTotal scanner detections updated from 9 to 10. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-26 15:32:47 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 193.162.133.218.
脅威対応 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.
