Skip to security report
Analytics Dashboard
Domain security report
daatalatalkhdrsh.framer.wiki favicon

daatalatalkhdrsh.framer.wiki

“Site Not Found | Framer”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Risk signals
VirusTotal detections: 14/91 Scam type: Impersonation
Aug 20, 2026
API
Registrar
CSC
Resolved IP
31.43.161.6
1 sources
The capture source is temporarily unavailable.
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 14. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

VirusTotal
VirusTotal
14 det.
CF Radar
Malicious
URLScan
URLScan
Report ↗
TLS Certificate
Within stored validity dates
Let's Encrypt · Hostname coverage not recorded
Observed status
Content unavailable 404
PhishDestroy
DestroyList
Listed

Source evidence

7 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

14 / 91

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

CF Radar

provider verdict: malicious

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

no community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

stored report

Observation time not recorded
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing
View full Cloudflare Radar report

Evidence Summary

Critical
VirusTotal
14/91
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

On 2026-10-01, daatalatalkhdrsh.framer.wiki returned an HTTP 404 status code, indicating that the requested page was not found at the time of the check. The domain was also listed in the PhishDestroy internal catalogue as of 2026-10-01.

Recorded Evidence

The domain daatalatalkhdrsh.framer.wiki was first observed on 2026-08-20. On 2026-10-01, an HTTP check recorded a 404 status code. VirusTotal reported on 2026-08-29 that 14 out of 91 scanners detected the domain. The domain appeared in the PhishDestroy internal listing as of 2026-10-01.

Interpretation

The available records provide a snapshot of daatalatalkhdrsh.framer.wiki's observed status at specific times. The HTTP 404 response indicates that the requested page was not found, while the VirusTotal and PhishDestroy records reflect how the domain was categorized by those sources.

Recommended Actions

To monitor daatalatalkhdrsh.framer.wiki, retain the HTTP status, VirusTotal results, and PhishDestroy listing as reference points for future checks. Compare new source records to these values to identify any changes. Avoid submitting sensitive information to the domain based on the recorded evidence.

Data coverage & collection

17 · datasets with records / 14 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
14 / 91 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
Cloudflare Radar
maliciousCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
CSC Corporate Domains, Inc.Collection time not recorded
Network & DNS
31.43.161.6 · 1 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt
Page captures
1 · retained captures
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
100/100 · mobile performance
Availability history
17 · stored state changes
Source observation history
2 · stored source events
IP reputation
Network-level observations
Not recorded in this report 14

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Page analysis
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

CSC Corporate Domains, Inc. · 31.43.161.6 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 14/100 4 reports Open ProxyEmail SpamWeb App Attack checked Aug 20, 2026
Platform provider CSC US(US)
HTTP Status404 Not Found
Time to First Unavailability 22 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 20, 2026

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
31.43.161.6
Network ASN
AS16509
Organization
Framer B.V
Observed location
Amsterdam, NL
Server header
Framer/6443c08
Nameservers 1
  • ns-772.awsdns-32.net

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid from
2026-08-03 08:34:30
Valid until
2026-11-01 08:34:29
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-08-20 07:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprint1b6f474373c2e47f7393f2114df412ea346ec24e6176e360621077fe8f0842ef

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 31.43.161.6rapiddns.io

Latest Classified Outcome 2026-10-17 01:11:45 UTC

Primary outcome Inactive reason: Hosting Placeholder 45% confidence
Attribution actor class: Hosting mechanism: Placeholder Page source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Resolved Registration: Unknown
Latest HTTP observation Inactive Hosting Placeholder actor class: Hosting Placeholder Page 45% 2026-10-17 01:11:45 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-08-20 00:28:09 UTC current episode first observed: 2026-10-01 01:35:56 UTC observed RIP window: 2026-08-20 00:28:09 UTC → 2026-10-01 01:35:56 UTC · 1,009.13h midpoint estimate ≈ 2026-09-10 01:02:02 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.
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

14 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 17 detections
alphaMountain.ai
Cluster25
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
Kaspersky
Lionic
MalwareURL
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of daatalatalkhdrsh.framer.wiki · checked Aug 20, 2026

100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.76s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
1009.13
Estimate basis
Bounded by observations
Estimate precision
very_low

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
Framer/24ab00f

Scanner note: hosting_placeholder: raw=placeholder; http=404; via=https_proxy; server=Framer/24ab00f

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
On demand

No live-check result has been retained.

Timeline & response

Collection history, report status and investigation channels

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.
  1. Domain Status Transition 2026-09-11 01:14:58 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  2. Threat First Observed 2026-08-20 00:33:13 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive.
Stored observation history19

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→inactive

    hosting_placeholder · placeholder_page

  3. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→inactive

    hosting_placeholder · placeholder_page

  5. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

Earlier observations 14
  1. Availability monitor · Recorded state

    Unknown→inactive

    hosting_placeholder · placeholder_page

  2. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→inactive

    hosting_placeholder · placeholder_page

  4. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→inactive

    hosting_placeholder · placeholder_page

  6. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  7. Availability monitor · Recorded state

    Unknown→inactive

    hosting_placeholder · placeholder_page

  8. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  9. Availability monitor · Recorded state

    Unknown→inactive

    hosting_placeholder · placeholder_page

  10. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  11. Availability monitor · Recorded state

    Unknown→inactive

    hosting_placeholder · placeholder_page

  12. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  13. Availability monitor · Recorded state

    Reachable→Unavailable

  14. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Monitoring

11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
daatalatalkhdrsh.framer.wiki detected and queued for full analysis
Aug 20, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Cloudflare Radar Report
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.
VirusTotal
14/91 recorded on VirusTotal
Aug 29, 2026
CF Radar: Malicious
Cloudflare Radar classified this domain as phishing
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Sep 11, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Aug 20, 2026
Content Observed Unavailable
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 11, 2026
Time to First Unavailability
530 hours elapsed from detection to the first unavailable observation.
How we investigate & report

Public scans, evidence and abuse channels

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 14 det. ChainPatrol URLQuery SSL Labs Hostname coverage not recorded CF Radar Malicious WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including daatalatalkhdrsh.framer.wiki)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: daatalatalkhdrsh.framer.wiki

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Site Not Found | Framer”.

VirusTotal detections for daatalatalkhdrsh.framer.wiki: 14 (2026-08-29 02:26:08 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

submit an appeal or review the FAQ page.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/daatalatalkhdrsh.framer.wiki"
  title="PhishDestroy threat report for daatalatalkhdrsh.framer.wiki"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>