VirusTotal
5 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Bot Verification”
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.
5 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
Report A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
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.
On 2026-10-01, om.agfoodcompany.online returned an HTTP status 200 during a recorded check, indicating a successful response at that time. This domain was first recorded on 2026-07-27, providing an earlier baseline for its activity.
VirusTotal reported 5 detections out of 89 scanners for om.agfoodcompany.online on 2026-09-14. The PhishDestroy internal listing included this domain as of 2026-10-01. An SSL certificate scan on 2026-08-13 identified Let's Encrypt / YE2 as the certificate issuer.
The evidence from VirusTotal, PhishDestroy, and the SSL scan each reflect different points in time, which means their observations are not directly synchronized. The HTTP check and PhishDestroy listing share the same date, while the VirusTotal and SSL scan provide earlier snapshots. These differences in timing should be considered when comparing or interpreting the records from each source.
For ongoing review of om.agfoodcompany.online, retain the dated findings from VirusTotal, PhishDestroy, and the SSL scan, as well as the HTTP check. Compare any new observations to these specific records to track changes accurately. Avoid submitting sensitive information to om.agfoodcompany.online until all available evidence has been thoroughly evaluated.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
LiteSpeedScanner note: captcha: raw=captcha; http=200; via=https_proxy; server=LiteSpeed
For the registrable domain agfoodcompany.online behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
ns107.asurahosting.commail.om.agfoodcompany.onlinepriority 10Location describes the IP network.
f8dd91209ab56621307bfe8ebacb8ff57cfadf9057203b70183caad72c9e4148Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
8 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 community report
CategoryPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-07-22T23:28:00.480Z.
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