VirusTotal
14 / 92
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
Unicode spellingbitrefîll.com
Assessment based on the stored source evidence below. Review 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.
14 / 92
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
2 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Report stored; detailed verdict not recorded
Alerts refer to the preserved scan. They do not describe the current state of the site.
7 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Report stored; verdict not recorded
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
xn--bitrefll-q2a.com was recorded with multiple security observations, including a VirusTotal detection count on 2026-10-15. The domain also appeared on two external blocklists, which adds further context to its profile.
On 2026-10-15, VirusTotal documented 14 detections out of 92 scanners for xn--bitrefll-q2a.com. The same day, OTX listed seven pulses referencing the domain. MetaMask and SEAL both included the domain on their external blocklists as of 2026-10-15. PhishDestroy also listed the domain internally. The registrar was recorded as DYNADOT LLC, and the SSL certificate was issued by Let's Encrypt / YR1.
VirusTotal provides a quantitative record of how many security scanners flagged xn--bitrefll-q2a.com, which is a direct measurement of its recognition among threat intelligence tools. OTX contributes additional context by tracking pulses, which are community-driven signals about domains. The presence on MetaMask and SEAL blocklists, as well as PhishDestroy's internal listing, expands the scope of recorded security attention. These sources collectively document the domain's status across several security intelligence platforms on the same date.
For xn--bitrefll-q2a.com, preserve all VirusTotal, OTX, MetaMask, SEAL, and PhishDestroy records for ongoing comparison. Review future blocklist entries and detection counts to track changes in security observations. Compare new findings with the documented 2026-10-15 evidence to assess any shifts in the domain's recorded profile.
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.
These checks have no retained result. This does not mean they passed or that a scan is running.
ns1.dyna-ns.netns2.dyna-ns.netLocation describes the IP network.
93d47433878474f6c3f6d0c45ed0dcc9588cc14d361108c58347bfa20963b855www.xn--bitrefll-q2a.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of xn--bitrefll-q2a.com · checked Oct 15, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://xn--bitrefll-q2a.com/https://www.google.com/Content-Type: text/html; charset=UTF-8Cache-Control: private, max-age=0Content-Encoding: gzipServer: gws8720df457a93b97d3cdd7c05714c8e255a1969085844eb247756b869dbea636aSec-CH-Prefers-Color-Schemeh3=":443"; ma=2592000,h3-29=":443"; ma=2592000private, max-age=0gzipobject-src 'none';base-uri 'self';script-src 'nonce-R3iIPkrjS_BmA49XAgsnNA' 'strict-dynamic' 'report-sample' 'unsafe-eval' 'unsafe-inline' https: http:;report-uri https://csp.withgoogle.com/csp/gws/other-hptext/html; charset=UTF-8same-origin-allow-popups; report-to="gws"Thu, 15 Oct 2026 15:59:13 GMT-1; rel="compression-dictionary"CP="This is not a P3P policy! See g.co/p3phelp for more info."unload=(){"group":"gws","max_age":2592000,"endpoints":[{"url":"https://csp.withgoogle.com/csp/report-to/gws/other"}]}gwschunkedSAMEORIGIN0Values retained by the collector; long values may be shortened during collection.
Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.
/robots.txt
A legacy response is stored, but it does not establish whether the file exists.
/sitemap.xml
A legacy response is stored, but it does not establish whether the file exists.
/.well-known/security.txt
A legacy response is stored, but it does not establish whether the file exists.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Local archived 2026-10-15 15:59:14 UTC62.60.226.163.9 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
PD-20261015-4F4843 Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive