The domain altaweb.hu was included in the publisher's PhishDestroy internal listing as of 2026-10-08, and was also recorded in a VirusTotal scan on 2026-10-04. These observations provide dated reference points for the domain's evaluation by different security sources.
Recorded Evidence
VirusTotal checked altaweb.hu on 2026-10-04, with 6 detections out of 92 scanners. The domain was added to the publisher's PhishDestroy internal listing on 2026-10-08. Its registration date is recorded as 2008-06-24.
Interpretation
The VirusTotal and PhishDestroy records document how altaweb.hu was assessed by external scanners and the publisher's own monitoring at specific times. These sources offer independent perspectives on the domain's history and attention from security systems.
Recommended Actions
Anyone reviewing altaweb.hu should reference both the VirusTotal and PhishDestroy records for analysis. It is important to preserve these dated source observations for future comparison and ongoing monitoring.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo 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
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Certificate hostname mismatch·
Issued by DigiCert Inc / RapidSSL TLS RSA CA G1· stored validity ends in 5 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
185.75.192.3
Nameservers 3
ns1.boga.hu
ns2.boga.hu
ns3.boga.hu
Location describes the IP network.
TLS certificate
Issuer
DigiCert Inc / RapidSSL TLS RSA CA G1
Valid from
2025-10-14 00:00:00
Valid until
2026-10-13 23:59:59
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-08 01:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint77162aed2b415da86220c6c456c3d3fd389df28a6aa129826b6c6e41501c4830Certificate names · 1 SANs
elin.hu
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-08 00:06:06 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-08 00:06:06 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.
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.
Threat First Observed2026-10-08 00:06:06 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 185.75.192.3.
Threat Response Pipeline
Discovery
Analysis
Monitoring
6 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
4 evidence signal groups linked0 reports recordedUnverified
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.
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 →
