The domain novbil.framer.website was registered on 21 February 2026 through CSC Corporate Domains, Inc. Its authoritative name servers are part of the Amazon Route 53 pool (ns-1243.awsdns-27.org, ns-1818.awsdns-35.co.uk, ns-336.awsdns-42.com, …). DNS resolution points to the Amazon‑owned address 35.71.142.77, which is announced by AS16509 (Amazon.com, Inc.) and located in the United States. An SSL certificate labeled “E8” is present, but the site currently returns an HTTP 404 response with the page title “Site Not Found | Framer”. The host is listed as offline in the latest check and has been taken down. Multiple detection engines have flagged the domain: VirusTotal records 14 positive detections out of 93 scanners, and the domain appears on one external security blocklist.
PhishDestroy has explicitly blocked the domain, indicating prior association with phishing activity. No additional public threat‑intel feeds (OTX, Safe Browsing, etc.) are referenced in the supplied data. The available evidence points to a short‑lived phishing infrastructure that was likely used shortly after registration and subsequently seized or removed. However, the exact payload, targeted brand, or phishing kit cannot be confirmed because the page content is unavailable and only a generic “Site Not Found” title is observed.
Consequently, the full scope of the campaign—such as victim count, lure vectors, or credential‑stealing mechanisms—remains unknown. Defenders should continue to block the domain at DNS and network layers, monitor the associated IP address for any re‑use, and add the identifier to internal threat‑intel feeds. Periodic re‑resolution checks are advised to detect possible re‑hosting. Because the domain is already offline, immediate remediation focuses on preventing future reuse of the same IP range and ensuring that any email or URL filters that previously flagged the domain remain active.
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 timelinecurrent episode first observed: 2026-10-01 01:01:03 UTCfirst terminal observation: 2026-10-01 01:01:03 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.
Google PageSpeed Insights — mobile performance audit of novbil.framer.website· checked Mar 2, 2026
98
Good
Performance
FCP
1.8s
First Contentful Paint
LCP
1.8s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.8s
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.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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)
