Analysis of the domain servertech-restore-optus.framer.website indicates a brand impersonation campaign targeting Optus, as evidenced by the page title 'Optus Webmail' and explicit classification in threat intelligence sources. The domain was registered on November 19, 2021, through CSC Corporate Domains, Inc., and is currently offline, returning an HTTP 404 status. Infrastructure analysis reveals hosting on Amazon Web Services (AS16509) at IP 52.223.52.2, located in the United States, with nameservers distributed across AWS DNS endpoints. The SSL certificate is issued by Let's Encrypt, a common choice for both legitimate and malicious sites, providing no definitive signal of intent.
Detection data shows the domain appears on one security blocklist and is flagged by 14 of 95 security vendors in VirusTotal, suggesting moderate but not universal recognition as malicious. The scam type is classified as brand impersonation, consistent with the observed page title and known targeting of Optus. Technologies detected include Framer Sites, React, HSTS, and HTTP/3, which are not inherently malicious but are frequently used in phishing campaigns for their ease of deployment and modern web capabilities. Defenders should treat this domain as a confirmed threat due to its offline status, blocklist presence, and vendor detections.
While the exact content of the site is not analyzed, the combination of brand impersonation, page title, and detection data provides sufficient evidence for blocking and monitoring. The domain's registration age does not preclude malicious use, as older domains are often repurposed for phishing. Network defenders are advised to block the domain and IP, monitor for related subdomains or redirects, and review logs for connections to 52.223.52.2 or the listed nameservers. Further investigation into the registrar's abuse handling and AWS hosting context may provide additional context for takedown or attribution efforts.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Attributionactor class: Hostingmechanism: Placeholder Pagesource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: ResolvedRegistration: Unknown
Latest HTTP observation非活动Hosting Placeholderactor class: HostingPlaceholder Page45%2026-10-13 01:00:21 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-02-14 16:36:28 UTCcurrent episode first observed: 2026-10-01 01:01:03 UTCobserved RIP window: 2026-02-14 16:36:28 UTC → 2026-10-01 01:01:03 UTC · 5,480.41hmidpoint estimate ≈ 2026-06-08 20:48:45 UTC · precision very low · basis bounded
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.
技术 · 4 identified
F
Framer Sites
R
React
JavaScript frameworks
JavaScript library for building user interfaces with component-based architecture.
H
HSTS
安全
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
H
HTTP/3
Miscellaneous
Third major version of HTTP protocol, built on QUIC for faster, more reliable connections.
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.
16 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.
(US)
