VirusTotal
5 / 91
“abl.anantaagi.com”
abl.anantaagi.com was recorded responding with HTTP status 308 on 2026-10-02, indicating a specific server behavior at that time. The domain was also included in the PhishDestroy internal listing, which may warrant further attention.
On 2026-10-02, abl.anantaagi.com returned an HTTP 308 status code. The domain was first observed on 2026-09-14. VirusTotal checked the domain on 2026-09-27, reporting 5 detections out of 91 scanners. The SSL certificate was issued by Let's Encrypt / YE1 and scanned on 2026-09-26. The PhishDestroy internal listing included the domain as of the latest evidence.
The evidence for abl.anantaagi.com spans several security sources, providing insight into its observed network behavior and security assessment. The HTTP status and VirusTotal results, combined with its inclusion in the PhishDestroy internal listing, allow for a comparison of how the domain was evaluated by different monitoring tools within a defined timeframe.
For future analysis of abl.anantaagi.com, it is advisable to preserve the VirusTotal scan results, HTTP response record, and the PhishDestroy internal listing. Comparing these records can help track any changes in the domain's observed characteristics. Continued monitoring using these sources is recommended to identify any new developments.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
CaddyScanner note: redirect: raw=redirect_308; http=308; via=http_proxy; location=https://abl.anantaagi.com/; server=Caddy
kristina.ns.cloudflare.comLocation describes the IP network.
a7037a704032a6595a51a3f8f22294e38cc68566e21670ffd749ebba163462a2Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
6 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-09-14T11:19:34.763Z.
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