VirusTotal
15 / 91
“xn--bitreill-cz9c.com”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 18 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
xn--bitreill-cz9c.com — Останній відомий активний (HTTP 200). Тип шахрайства: Impersonation. Зведення доказів: VirusTotal 15/91 (ChainPatrol, alphaMountain.ai, BitDefender, CRDF, CyRadar); URLQuery 2 det.; Spamhaus DBL_SPAM; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. Реєстратор: Dynadot.
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
15 / 91
2 det.
ПовідомитиDBL_SPAM
4 community references
Повідомитиprovider verdict: suspicious
Повідомитизбережений звіт
Повідомити Аналіз завершено
Повідомити80/100
ПовідомитиChecked; no threat flag recorded
ПовідомитиStored evidence for xn--bitreill-cz9c.com: VirusTotal recorded 5 detections among 89 scanners on 2026-09-23. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for xn--bitreill-cz9c.com. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 5 detections among 89 scanners in the stored snapshot dated 2026-09-23. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-23 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
MetaMask and SEAL are recorded as named external blocklist observations for xn--bitreill-cz9c.com in the snapshot dated 2026-09-23. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains xn--bitreill-cz9c.com as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
The record first observed xn--bitreill-cz9c.com on 2026-09-23. The MetaMask and SEAL blocklist snapshot is dated 2026-09-23 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-11. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
For xn--bitreill-cz9c.com, the registrar field records Dynadot Inc; this is kept as an exact source value. The source stores 62.60.226.163 as the observed address in this record. The registration date for xn--bitreill-cz9c.com is recorded as 2026-09-11. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
The xn--bitreill-cz9c.com record states that VirusTotal recorded 5 detections among 89 scanners on 2026-09-23. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-23. PhishDestroy remains a separate publisher catalogue entry in the stored record. For xn--bitreill-cz9c.com, the registrar field records Dynadot Inc; this remains separate from the other source fields. The observed address field in this record contains 62.60.226.163. The supported conclusion is bounded to the exact stored observations for xn--bitreill-cz9c.com. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to xn--bitreill-cz9c.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain xn--bitreill-cz9c.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to xn--bitreill-cz9c.com. The stored record does not justify extending that rule to 62.60.226.163 or to other infrastructure records.
Збережені дані спостережень за взаємодією веб-сканера та браузера для цього хоста, а також перевірка відбитків у режимі реального часу для систем розподілу трафіку типу «Кейтаро».
nginx/1.30.3Примітка щодо сканера: alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.30.3
ns1.dyna-ns.netns2.dyna-ns.netLocation describes the IP network.
cddde093d6647d4cca913fbcf90ea0cc2ff962ef4c86fcbb89e8420d451dbd1bSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
62.60.226.163. 11 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-20260923-221F84 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
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
Template-based draft · optional AI wording assistance requires separate consent
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога