VirusTotal
13 / 89
“Jerry and Kristi – Our 50 state adventure to celebrate our 50th birthdays”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@godaddy.com.
The latest stored availability evidence still shows the domain reachable; 29 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.
jerrybeers.com — Останній відомий активний (HTTP 200). Тип шахрайства: Impersonation. Зведення доказів: VirusTotal 13/89 (ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua Dao, Forcepoint ThreatSeeker); URLQuery 5 alerts; 1 external blocklist match (ScamSniffer); CF Radar malicious; PhishDestroy score 100/100. Реєстратор: GoDaddy.
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
13 / 89
5 threat-system alerts
Повідомитиprovider verdict: malicious
Повідомити6 community references
Повідомитизбережений звіт
Повідомити Аналіз завершено
ПовідомитиChecked; no threat flag recorded
Повідомити| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| OpenDNS | jerrybeers.com |
phishing | Phishing Block |
| DigiCert UltraDNS | jerrybeers.com |
malicious | Sinkholed |
| Cloudflare DNS | jerrybeers.com |
malicious | Sinkholed |
| DNS4EU | jerrybeers.com |
malicious | Sinkholed |
| Quad9 DNS | jerrybeers.com |
malicious | Sinkholed |
Stored evidence for jerrybeers.com: VirusTotal recorded 12 detections among 89 scanners on 2026-09-12. That ratio reproduces the stored check in its original units and is not converted into another measure. ScamSniffer appear as named external blocklist observations for jerrybeers.com. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 12 detections among 89 scanners in the stored snapshot dated 2026-09-12. 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-12 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.
ScamSniffer are recorded as named external blocklist observations for jerrybeers.com in the snapshot dated 2026-09-12. The stored ScamSniffer blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains jerrybeers.com as a publisher record. That PhishDestroy record is counted separately from the ScamSniffer 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 jerrybeers.com on 2026-09-12. The ScamSniffer blocklist snapshot is dated 2026-09-12 and remains a separate event in the stored timeline. The registration date is separately recorded as 2000-08-25. 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.
The source stores 109.205.186.14 as the observed address in this record. The registration date for jerrybeers.com is recorded as 2000-08-25. 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 jerrybeers.com record states that VirusTotal recorded 12 detections among 89 scanners on 2026-09-12. ScamSniffer remain named blocklist observations from the snapshot dated 2026-09-12. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 109.205.186.14. The supported conclusion is bounded to the exact stored observations for jerrybeers.com. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to jerrybeers.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain jerrybeers.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and ScamSniffer 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 jerrybeers.com. The stored record does not justify extending that rule to 109.205.186.14 or to other infrastructure records.
Збережені дані спостережень за взаємодією веб-сканера та браузера для цього хоста, а також перевірка відбитків у режимі реального часу для систем розподілу трафіку типу «Кейтаро».
BitNinja-WafProПримітка щодо сканера: alive_content: raw=ok; http=200; via=https_proxy; server=BitNinja-WafPro
ns3.hostek.comns4.hostek.comaspmx.l.google.compriority 10alt1.aspmx.l.google.compriority 20alt2.aspmx.l.google.compriority 20aspmx5.googlemail.compriority 30aspmx4.googlemail.compriority 30aspmx3.googlemail.compriority 30aspmx2.googlemail.compriority 30Location describes the IP network.
4ee2a60ee369e6c45895133f5a0a37adddf24515f67c8cdcb0ab38a810dc57c7jerrybeers.com.cp8.ezhostingserver.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 jerrybeers.com · checked Sep 12, 2026
109.205.186.14. 12 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.
1 повідомлення спільноти
КатегоріяPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as phishing. Associated tags: credentials harvesting, brand impersonation. Threat detected at 2024-02-02T14:51:41.947Z.
PD-20260912-DA8FC2 Recipient: abuse@godaddy.com Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
Template-based draft · optional AI wording assistance requires separate consent
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога