Analysis of the domain mytalktalkprovider4u.framer.website shows it has been classified as a generic phishing site with an elevated risk rating. The domain was created on November 19, 2021 and is registered through CSC Corporate Domains, Inc. Infrastructure profiling reveals that the hostname resolves to the Amazon-owned address 52.223.52.2, located in the United States under ASN 16509, and is served by the nameservers ns-1243.awsdns-27.org, ns-1818.awsdns-35.co.uk, ns-336.awsdns-42.com, and ns-792.awsdns. The web server presented a valid Let's Encrypt SSL certificate (issuer E7) and supported modern transport features including HSTS and HTTP/3, while the front‑end stack was identified as Framer Sites built on React.
A HTTP request to the root returned a 404 status, indicating that the original content is no longer publicly reachable, and the domain is currently marked offline. Threat intelligence sources have recorded 11 of 93 VirusTotal scanners flagging the host, and PhishDestroy has actively blocked the domain; it also appears on a single external security blocklist. While the exact phishing landing page has not been captured, the combination of a recent page title "My Framer Site" and the technical fingerprint aligns with known phishing kit deployments that leverage Framer hosting for short‑lived credential‑harvesting pages.
Defenders should continue to deny DNS resolution for the domain, add it to internal blocklists, and monitor the associated IP range for re‑use, given the low cost of repurposing cloud‑based infrastructure. Ongoing observation of the registrar and nameserver configuration is advised to detect any re‑registration attempts that could revive the phishing campaign.
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:25 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-02-14 16:34:24 UTCcurrent episode first observed: 2026-10-01 01:01:09 UTCobserved RIP window: 2026-02-14 16:34:24 UTC → 2026-10-01 01:01:09 UTC · 5,480.45hmidpoint estimate ≈ 2026-06-08 20:47:46 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.
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.
(US)
