VirusTotal
4 / 89
“Receipt Investigation”
On 2026-10-01, affirminvestigation.com returned an HTTP status 302 according to a recorded check, indicating a redirect response at that time. The domain was first observed on 2026-08-28, and has evidence from multiple sources within a short observation window.
VirusTotal reported 4 detections out of 89 scanners for affirminvestigation.com on 2026-09-13. OTX recorded 2 pulses involving the domain on the same date. The PhishDestroy internal listing was marked as true, and the SSL certificate scan was completed on 2026-09-17 with Let's Encrypt / YR2 as the issuer.
These source records provide distinct perspectives on affirminvestigation.com, including detection counts, pulse records, and listing status. The HTTP 302 response documents only the redirect observed on its check date, while VirusTotal and OTX reflect third-party scanning and reporting. The SSL certificate scan and internal listing offer additional context about the domain's technical setup and catalog status.
For affirminvestigation.com, retain the VirusTotal detection record and PhishDestroy internal listing as separate evidence sources. Compare the OTX pulse data with other records to identify any overlap in reporting. Recheck the HTTP response to track any changes in status codes. Preserve the SSL certificate scan for future reference and avoid submitting sensitive information to the domain based on the recorded evidence.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
LiteSpeedScanner note: redirect: raw=redirect_302; http=302; via=https_direct; location=https://receiptinvestigation.com/; server=LiteSpeed
ns9.hawkhost.comLocation describes the IP network.
dd5974624ae52782af1406d67d540a48db41fc2aeb05723a03a707a6ce2c3e70www.affirminvestigation.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
9 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-08-27T16:11:55.608Z.
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