Skip to content

Hostname

balhasengineering.com

Last fetched

balhasengineering.com resolves to 50.87.35.106, announced in 50.87.32.0/21 by ORACLE-BMC-31898 - Oracle Corporation in US. balhasengineering.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · balhasengineering.comRouting diversity1.5/10Peering density8.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/balhasengineering.com

Resolution chain

IPv6 resolution

No AAAA record for balhasengineering.com is recorded in WhisperGraph.

Attribution

oracle

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:93
Registrant organisation
barmaja
Contact emails
husseinalikhansa@gmail.com, fa75f2a21b9e4fcdb4d7b4eff7c7ef07.protect@withheldforprivacy.com, 333c14cd323f84cb1d82828a04e73adc5a512416@privatedomain.gkg.net, 5fa9fbfb1f37b992e0004f70f5779ef8ba7c03f6@privatedomain.gkg.net, 6b708f26317264ba65b93cc8c087a8fcc017bb90@privatedomain.gkg.net, 8708015c58129de671166bf04e289c88f821f292@privatedomain.gkg.net, 892aa1ae6135c12906bd246a96810b4f2e787f9c@privatedomain.gkg.net, 947771477a62547b19fc5b2f7c8f80fe28a72545@privatedomain.gkg.net, deede58f5ddc7c6854a2ebce950d93b76ab736dc@privatedomain.gkg.net

Subdomains

Subdomain
autoconfig.balhasengineering.com
autodiscover.balhasengineering.com
localhost.balhasengineering.com
mail.balhasengineering.com
www.balhasengineering.com

Showing 5 of 5 subdomains (5 per page).

Mail and authentication

Nameservers

  • ns1.amanaty.com
  • ns2.amanaty.com
  • ns1.rhostbh.com
  • ns2.rhostbh.com

MX records

  • balhasengineering.com

SPF policy

  • a: balhasengineering.com
  • mx: balhasengineering.com
  • include: rhostbh.com

Threat-feed evidence

History

Related pages

Pivot from balhasengineering.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "balhasengineering.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.