Hostname
acusense.ae
Last fetched
acusense.ae resolves to 104.21.56.192, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. acusense.ae is listed by 3 threat feeds; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 3 threat feeds. At least one source recommends blocking.
Categories: Phishing
- Threat feeds listing this
- 3
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:45:21 GMT
- Last seen on a feed
- Thu, 08 Oct 2026 00:42:35 GMT
Nutrition Label
Resolution chain
- 104.21.56.192
104.21.48.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.155.207
172.67.144.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 92.113.16.0
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.10
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.107
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.110
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.118
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.142
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.163
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.168
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.172
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.175
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.187
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.200
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.210
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.225
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.234
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.250
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.253
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.254
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for acusense.ae. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Company
- Company
- Acusense Tech
- Industry
- Security Systems Services
- Headquarters
- Dubai, United Arab Emirates
Technology
Acusense Tech has been observed using 40 technologies somewhere in its estate. This is observed use, not an exposure finding. The 20 most widely adopted:
- jQuery · javascript libraries
- Open Graph · content management system
- PHP · programming languages
- Google Fonts API · font scripts
- WordPress · blogs
- MySQL · database
- Priority Hints · performance
- JSON-LD · frameworks and libraries
- RSS · content management system
- HTTP/3 · web & portal technology
- Cloudflare · content delivery network
- jQuery Migrate · javascript libraries
- oEmbed · audio, video, graphics
- Sitelinks Search Box · web tools and plugins
- Really Simple Discovery · miscellaneous
- Cloudflare DNS · domain name services
- Google Maps · mapping and gis
- Yoast SEO · search engines
- Cloudflare CDN · content delivery network
- Swiper · javascript libraries
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for acusense.ae.
DKIM signing
No DKIM signing vendor is attributed to acusense.ae in WhisperGraph.
Nameservers
- albert.ns.cloudflare.com
- erin.ns.cloudflare.com
- horizon.dns-parking.com
- orbit.dns-parking.com
MX records
- mx.zoho.com
- mx2.zoho.com
- mx3.zoho.com
Threat-feed evidence
History
Related pages
Pivot from acusense.ae into the addresses, networks and registries it depends on.
Queries
This hostname's full card — resolution chain, registration, mail policy, DNSSEC and mail authentication.
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(ip:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap)
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH h, ip, ap, a, an, city, ipc
LIMIT 20
WITH h,
collect({ip: ip.name, prefix: ap.name, asn: a.name, network: an.name, city: city.name, country: ipc.name}) AS resolutions,
collect(a.name) AS asnNames,
collect(ap.name) AS prefixNames,
collect(ap.isMoas) AS moasFlags,
collect(ap.rpkiStatus) AS rpkiStatuses,
head(collect(a)) AS primaryAsn,
head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn,
collect(conflict.name) AS conflictAsns
OPTIONAL MATCH (h)-[:HAS_REGISTRAR]->(reg:REGISTRAR)
OPTIONAL MATCH (h)-[:REGISTERED_BY]->(org:ORGANIZATION)
OPTIONAL MATCH (h)-[:CHILD_OF]->(tld:TLD)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
collect(reg.name) AS registrars,
collect(org.name) AS organizations,
collect(tld.name) AS tlds
OPTIONAL MATCH (h)-[:HAS_EMAIL]->(em:EMAIL)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds,
collect(em.name) AS emails
OPTIONAL MATCH (h)-[:HAS_PHONE]->(ph:PHONE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails,
count(ph) AS phoneCount
OPTIONAL MATCH (h)<-[:MAIL_FOR]-(mx:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount,
collect(mx.name)[0..20] AS mxHosts
OPTIONAL MATCH (h)<-[:NAMESERVER_FOR]-(ns:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts,
collect(ns.name) AS nameservers
OPTIONAL MATCH (h)-[spf:SPF_A|SPF_EXISTS|SPF_INCLUDE|SPF_IP|SPF_MX|SPF_REDIRECT]->(spfTarget)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers,
collect({mechanism: type(spf), target: spfTarget.name})[0..50] AS spf
OPTIONAL MATCH (h)-[:SIGNED_WITH]->(alg:DNSSEC_ALGORITHM)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
collect(alg.name) AS dnssecAlgorithms
OPTIONAL MATCH (h)-[:DMARC_REPORTS_TO]->(dm:DMARC_RECIPIENT)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
collect(dm.name)[0..5] AS dmarcRecipients
OPTIONAL MATCH (h)-[:DKIM_SIGNED_BY]->(dk:VENDOR)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients,
collect(coalesce(dk.displayName, dk.name))[0..5] AS dkimVendors
OPTIONAL MATCH (h)-[:HAS_SIGNAL]->(hs:THREAT_SIGNAL_TYPE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients, dkimVendors,
collect(hs.name) AS dnsSignals
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN h.name AS name,
h.rank AS rank,
h.verdictLevel AS verdictLevel,
h.verdictScore AS verdictScore,
h.verdictBlocking AS verdictBlocking,
h.verdictCoverage AS verdictCoverage,
h.verdictAdvisory AS verdictAdvisory,
h.threatSources AS threatSources,
h.threatFirstSeen AS threatFirstSeen,
h.threatLastSeen AS threatLastSeen,
h.isTor AS isTor,
h.isVpn AS isVpn,
h.isProxy AS isProxy,
h.isC2 AS isC2,
h.isPhishing AS isPhishing,
resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
dnssecAlgorithms, dmarcRecipients, dkimVendors, dnsSignals,
h.companyName AS companyName,
h.companyIndustry AS companyIndustry,
h.companyHqCountry AS companyHqCountry,
h.companyHqCity AS companyHqCity,
asnPeerCountRun yourself →The observed subdomain count, to depth 3.
MATCH (h:HOSTNAME {name: $host})
CALL { WITH h MATCH (h)<-[:CHILD_OF*1..3]-(sub:HOSTNAME) RETURN count(sub) AS subdomainCount }
RETURN subdomainCountRun yourself →Technologies the company behind this domain has been observed running, most widely adopted first.
MATCH (:HOSTNAME {name: $host})-[:RUNS_TECHNOLOGY]->(t:TECHNOLOGY)
WITH t.name AS name, t.category AS category, t.adopterCount AS adopters
ORDER BY adopters DESC, name
WITH collect({name: name, category: category}) AS technologies, count(*) AS total
RETURN total, technologies[0..20] AS technologiesRun yourself →Peer companies (outbound SIMILAR_TO).
MATCH (:HOSTNAME {name: $host})-[:SIMILAR_TO]->(peer:HOSTNAME) RETURN peer.name AS host ORDER BY host LIMIT 8Run yourself →The parent company's domain and this company's domain portfolio (PARENT_OF).
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)<-[:PARENT_OF]-(parent:HOSTNAME)
WITH h, collect({host: parent.name, company: parent.companyName})[0..3] AS parents
OPTIONAL MATCH (h)-[:PARENT_OF]->(child:HOSTNAME)
RETURN parents, collect({host: child.name, company: child.companyName})[0..10] AS portfolioRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.