Hostname
galadevelopers.com
Last fetched
galadevelopers.com resolves to 195.35.44.16, announced in 195.35.44.0/24 by AS-HOSTINGER - Hostinger International Limited in IN. galadevelopers.com is listed by 2 threat feeds; reconciled level LOW.
Threat posture
1threat score (procedure-native scale)
LOWListed by 2 threat feeds.
- Threat feeds listing this
- 2
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:45:21 GMT
- Last seen on a feed
- Fri, 09 Oct 2026 23:55:35 GMT
Nutrition Label
Resolution chain
- 195.35.44.16
195.35.44.0/24 · AS-HOSTINGER - Hostinger International Limited · Mumbai, IN
- 2.57.91.26
2.57.91.0/24 · AS-HOSTINGER - Hostinger International Limited · Asheville, US
- 84.32.84.206
84.32.84.0/24 · AS-HOSTINGER - Hostinger International Limited · Vilnius, LT
- 84.32.84.217
84.32.84.0/24 · AS-HOSTINGER - Hostinger International Limited · Vilnius, LT
- 92.113.16.119
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.128
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.145
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.151
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.182
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.205
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.240
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.252
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.27
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.39
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.49
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.56
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
- 92.113.16.60
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
IPv6 resolution
Attribution
hostinger international
ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- chirag gala
- Contact emails
- domains@kragos.com, msgaladevelopers@gmail.com
Company
- Company
- Gala Developers
- Headquarters
- Jabalpur, India
Technology
Gala Developers has been observed using 17 technologies somewhere in its estate. This is observed use, not an exposure finding.
- jQuery · javascript libraries
- PHP · programming languages
- Font Awesome · font scripts
- HTTP/3 · web & portal technology
- Google Maps · mapping and gis
- Cart Functionality · e-commerce
- LiteSpeed · web servers
- YouTube · online community software
- cdnjs · content delivery network
- WhatsApp Business · live chat
- jsDelivr · content delivery network
- Hostinger · web hosting
- jQuery CDN · content delivery network
- WhatsApp · audio, video, graphics
- Hostinger CDN · content delivery network
- Laravel · web frameworks
- SweetAlert2 · javascript libraries
Subdomains
Showing 4 of 4 subdomains (4 per page).
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for galadevelopers.com.
DKIM signing
No DKIM signing vendor is attributed to galadevelopers.com in WhisperGraph.
Nameservers
- ns1.dns-parking.com
- ns2.dns-parking.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- mx1.hostinger.com
- mx2.hostinger.com
SPF policy
- include: _spf.mail.hostinger.com
Threat-feed evidence
History
Related pages
Pivot from galadevelopers.com 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.