VirusTotal
18 / 89
“Under Construction”
hemetek.com returned an HTTP status code of 200 when checked on 2026-10-01, indicating a successful response was recorded on that date. The domain is also listed in the PhishDestroy internal catalogue, which is a publisher-maintained record separate from external blocklists.
On 2026-10-01, hemetek.com was checked and returned an HTTP 200 status. VirusTotal, checked on 2026-09-16, reported 18 detections out of 89 scanners. OTX, checked on 2026-09-16, showed 5 pulses. The domain was first observed on 2026-09-04. Its registration date is 2001-03-22 with registrar PDR Ltd. d/b/a PublicDomainRegistry.com. An SSL scan on 2026-09-16 recorded the issuer as Let's Encrypt / YR1.
The recorded evidence from multiple sources provides a range of observations about hemetek.com, each reflecting its own context and method. The HTTP 200 response documents a successful request, while the VirusTotal and OTX records show results from their respective scans. The PhishDestroy internal catalogue listing is a distinct publisher record and does not overlap with external blocklists. Chronological details show the domain was tracked before the later checks, but the dates do not indicate a trend.
For hemetek.com, retain the VirusTotal and OTX records as separate source documents for future comparison. Keep the PhishDestroy internal catalogue entry as a distinct observation alongside the HTTP response record. When reviewing hemetek.com again, compare these records individually to assess any changes or new observations.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Microsoft-IIS/10.0Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=Microsoft-IIS/10.0
dns4.itsoul.commx.hemetek.com.cust.a.hostedemail.compriority 10Location describes the IP network.
a9da331e1e53d4ebc9817b00f9082b2007378e36bab01b993701195bfd670d17www.hemetek.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
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