VirusTotal
2 / 91
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“ð¨Create A Ticket”
Assessment based on the stored source evidence below. Review sources →
No stored capture is available for this domain.
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.
2 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
17 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
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.
This analysis documents the infrastructure and threat indicators associated with the domain aave.global, which was registered on May 07 2026 through GoDaddy.com, LLC. The authoritative name servers are ns75.domaincontrol.com and ns76.domaincontrol.com, both belonging to GoDaddy’s DNS service. DNS resolution points to IP address 15.197.225.128, an AWS Global Accelerator endpoint located in Canada, and the web server returns an HTTP 301 redirect. The TLS certificate presented is issued by GoDaddy.com under the GoDaddy TLS Intermediate CA DV – R1v1 chain, indicating a legitimate‑looking certificate but not confirming legitimate ownership. The site’s page title, displayed as “ð¨Create A Ticket”, suggests a ticket‑creation interface but no further content has been captured. Email routing is configured to Microsoft’s Outlook protection service (aave‑global.mail.protection.outlook.com). VirusTotal reports that 1 of 92 security vendors flagged the domain, and AlienVault OTX includes it in a single threat‑intel pulse. The domain appears on one public blocklist and is actively blocked by PhishDestroy. Gridinsoft assigns a trust score of 0/100, reinforcing the malicious assessment. The overall risk rating is high and the campaign is currently active. No additional payload, phishing page screenshots, or credential‑harvesting mechanisms have been observed; analysis is limited to the metadata above. Defenders should add aave.global to URL filtering and DNS block lists, monitor for outbound connections to 15.197.225.128, and enforce TLS inspection to detect any malicious payloads. Email gateways should verify the MX record and consider quarantining messages claiming to originate from this domain. Continuous threat‑intel monitoring is advised to capture any future changes to the site’s content or infrastructure.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
ip-100-74-5-78.eu-west-2.compute.internalScanner note: redirect: raw=redirect_301; http=301; via=https_proxy; location=http://discord.gg/complaint; server=ip-100-74-5-78.eu-west-2.compute.internal
For this gTLD, 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.
Edge-IP reputation is not attributed to this domain.
ns76.domaincontrol.comaave-global.mail.protection.outlook.compriority 0Location describes the IP network.
2852e8e2caad554767d72130275d69c345eba8eb0476e606a001aa2396a7f623Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
5 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.
95 stored lookalike domains
Reported by 1 community member, first seen May 7, 2026
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