Skip to content

Hostname

telnet.net.bd

Last fetched

telnet.net.bd resolves to 116.212.106.182, announced in 116.212.106.0/24 by TELNET-AS-BD-AP - Telnet Communication Limited Network and Transit Service Provider. Having Nationwide MPLS Network For Internet and Data Connectivity Through Telnets Own Network Infrastructure in BD. telnet.net.bd 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 · telnet.net.bdRouting diversity1.5/10Peering density4.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/telnet.net.bd

Resolution chain

IPv6 resolution

No AAAA record for telnet.net.bd is recorded in WhisperGraph.

Attribution

telnet

ORIGIN_AS

WHOIS identity

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

Mail and authentication

Nameservers

  • ns1.telnet.net.bd
  • ns2.telnet.net.bd
  • ns3.telnet.net.bd
  • 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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • ip: 120.50.16.0/24
  • ip: 120.50.30.0/29
  • ip: 116.212.105.112/28
  • ip: 120.50.31.12/32
  • ip: 116.212.104.64/28
  • ip: 120.50.30.64/29
  • ip: 116.212.111.70/32
  • ip: 120.50.30.80/28
  • include: _spf.google.com

Threat-feed evidence

History

Related pages

Pivot from telnet.net.bd 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: "telnet.net.bd"})-[: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.