Skip to content

Hostname

infosoft.tr

Last fetched

infosoft.tr resolves to 185.165.46.32, announced in 185.165.46.0/24 by BurtiNET - BNET BULUT Bilisim Hizmetleri Tic. Ltd. Sti. in TR. infosoft.tr 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 · infosoft.trRouting diversity2.4/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.8/10canon.whisper.security/host/infosoft.tr

Resolution chain

IPv6 resolution

No AAAA record for infosoft.tr is recorded in WhisperGraph.

Attribution

bnet bulut bilisim hizmetleri tic sti

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for infosoft.tr. 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.

Subdomains

Subdomain
mail.infosoft.tr
ns1.infosoft.tr
ns2.infosoft.tr
ns3.infosoft.tr
www.infosoft.tr

Showing 5 of 5 subdomains (5 per page).

Mail and authentication

Nameservers

  • ns27.burtinet.com
  • ns1.cprapid.com
  • ns2.cprapid.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
  • ns1.netvay.com.tr
  • ns2.netvay.com.tr
  • ns1.infosoft.tr
  • ns2.infosoft.tr

MX records

  • infosoft.tr

SPF policy

  • include: relay.mailbaby.net
  • a: infosoft.tr
  • mx: infosoft.tr
  • ip: 185.165.46.3
  • ip: 185.165.46.32

Threat-feed evidence

History

Related pages

Pivot from infosoft.tr 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: "infosoft.tr"})-[: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.