Hostname
jhsi.com
Last fetched
jhsi.com resolves to 100.25.198.255, announced in 100.24.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. jhsi.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 100.25.198.255
100.24.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 100.50.65.76
100.48.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 107.23.66.193
107.23.0.0/17 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.210.167.193
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.216.236.41
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.218.101.106
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.219.40.217
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.221.253.237
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.224.231.82
3.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.234.147.205
34.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.21.156.226
52.20.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.70.31.81
52.70.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for jhsi.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of jhsi.com owner
- Contact emails
- ax3fs3n45d6@networksolutionsprivateregistration.com, ce42j54x7jj@networksolutionsprivateregistration.com, dv5gd8nt3zp@networksolutionsprivateregistration.com, f78v79bx95n@networksolutionsprivateregistration.com, h28wj9sm76f@networksolutionsprivateregistration.com, h52a75ys535@networksolutionsprivateregistration.com, kw3kp3db34t@networksolutionsprivateregistration.com, pp2t65m53qn@networksolutionsprivateregistration.com, q24d87at5ec@networksolutionsprivateregistration.com, s74wj95f7vk@networksolutionsprivateregistration.com, ta6ks5tr534@networksolutionsprivateregistration.com, wz5fa47z8yp@networksolutionsprivateregistration.com, xp4qr73z3wz@networksolutionsprivateregistration.com, 17d9d0db-d8bd-4a4f-a1b4-d30bed1b7904@identity-protect.org, 2ebc55a2-7f16-4c35-b5c7-869bb7ccbe2c@identity-protect.org, 2f8f5ed0-4b5e-496d-ae75-4fdd35dc1604@identity-protect.org, 495ce59c-cca8-4990-8ea0-780cdb506d94@identity-protect.org, 9a39cba6-c13b-41b6-81ea-5b627a31dab0@identity-protect.org, 9de7796b-9fb6-4f56-a8a6-a23ba6bfa166@identity-protect.org, a3c9a439-aef4-43b2-bac0-b2e4bfe949b7@identity-protect.org and 1 more
Company
- Company
- Jordan Health Services, Inc.
- Industry
- Hospitals and Health Care
- Headquarters
- Mount Vernon, United States
Technology
Jordan Health Services, Inc. has been observed using 34 technologies somewhere in its estate. This is observed use, not an exposure finding. The 20 most widely adopted:
- jQuery · javascript libraries
- Google Analytics · intelligence and analytics
- React · javascript frameworks
- Lodash · javascript libraries
- Webpack · build automation
- RequireJS · javascript frameworks
- Windows Server · operating systems
- Microsoft ASP.NET · web frameworks
- Microsoft Word · document management systems
- TweenMax · javascript frameworks
- Microsoft · miscellaneous
- Microsoft Office · office suites
- Microsoft Excel · editors
- Zepto · javascript libraries
- AngularJS · javascript frameworks
- SQL · data management
- Microsoft Outlook · email
- Power BI · business intelligence
- Microsoft Windows · it infrastructure
- Microsoft SQL Server · data management
Peer companies
Subdomains
| Subdomain |
|---|
| dwebmail.jhsi.com |
| forms.jhsi.com |
| jordanwebstore.jhsi.com |
| mdma.jhsi.com |
| mwebmail.jhsi.com |
| sa.jhsi.com |
| vtach.jhsi.com |
| vtach1.jhsi.com |
| webmail.jhsi.com |
| www.jhsi.com |
Showing 10 of 10 subdomains (10 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for jhsi.com.
DKIM signing
No DKIM signing vendor is attributed to jhsi.com in WhisperGraph.
Nameservers
- ns-371.awsdns-46.com
- ns-726.awsdns-26.net
- ns-1107.awsdns-10.org
- ns-1649.awsdns-14.co.uk
MX records
- jhsi-com.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from jhsi.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.