Hostname
pro24-jlt.com
Last fetched
pro24-jlt.com resolves to 141.136.33.68, announced in 141.136.33.0/24 by AS-HOSTINGER - Hostinger International Limited in GB. pro24-jlt.com is listed by 1 threat feed; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONEListed by 1 threat feed. Advisory: score-zero-listing.
- Threat feeds listing this
- 1
- Verdict coverage
- listing-stopped
- First seen on a feed
- Wed, 26 Aug 2026 14:49:47 GMT
- Last seen on a feed
- Tue, 06 Oct 2026 07:52:43 GMT
Nutrition Label
Resolution chain
- 141.136.33.68
141.136.33.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2643123
- 147.79.120.184
147.79.120.0/21 · AS-HOSTINGER - Hostinger International Limited · geoname:5308655
- 77.37.76.65
77.37.76.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:5308655
- 84.32.84.213
84.32.84.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:593116
- 92.113.16.107
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.113
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.114
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.128
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.13
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.134
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.137
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.145
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.149
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.155
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.158
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.18
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.190
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.207
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.227
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
- 92.113.16.234
92.113.16.0/24 · AS-HOSTINGER - Hostinger International Limited · geoname:2925533
IPv6 resolution
Attribution
hostinger international
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1636
- Registrant organisation
- ali tavari
- Contact emails
- itiskey@yahoo.com
Company
- Company
- Pro24 Jlt
- Industry
- Consumer Services
- Headquarters
- Dubai, United Arab Emirates
Technology
Pro24 Jlt has been observed using 50 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
- Font Awesome · font scripts
- Google Analytics · intelligence and analytics
- 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
- Google Tag Manager · tag management
- oEmbed · audio, video, graphics
- Sitelinks Search Box · web tools and plugins
- Google Search Console · performance
- Really Simple Discovery · miscellaneous
- Yoast SEO · search engines
Peer companies
Subdomains
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for pro24-jlt.com.
DKIM signing
No DKIM signing vendor is attributed to pro24-jlt.com in WhisperGraph.
Nameservers
- ns1.dns-parking.com
- ns2.dns-parking.com
MX records
- mx1.titan.email
- mx2.titan.email
SPF policy
- include: spf.titan.email
Threat-feed evidence
History
Related pages
Pivot from pro24-jlt.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) WHERE a.name IS NOT NULL
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) WHERE conflict.name IS NOT NULL
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.