Skip to content

Hostname

rangosang.ir

Last fetched

rangosang.ir resolves to 88.135.68.100, announced in 88.135.68.0/24 by MIZBANFA - Dade Pardazan Fahim Shahin Shahr (Ltd) in IR. rangosang.ir 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 · rangosang.irRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/rangosang.ir

Resolution chain

IPv6 resolution

No AAAA record for rangosang.ir is recorded in WhisperGraph.

Attribution

dade pardazan fahim shahin shahr

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for rangosang.ir. 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
autodiscover.rangosang.ir
cpanel.rangosang.ir
cpcalendars.rangosang.ir
cpcontacts.rangosang.ir
ftp.rangosang.ir
mail.rangosang.ir
webdisk.rangosang.ir
webmail.rangosang.ir
www.rangosang.ir

Showing 9 of 9 subdomains (9 per page).

Mail and authentication

Nameservers

  • dns1.mizbanfadns.net
  • dns2.mizbanfadns.net
  • dns3.mizbanfadns.net
  • dns4.mizbanfadns.net
  • 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

  • mail.mizbanfalocal.com

SPF policy

  • a: rangosang.ir
  • mx: rangosang.ir
  • include: relay.mailchannels.net
  • ip: 88.135.68.100
  • ip: 88.135.68.11
  • ip: 88.135.68.26
  • ip: 88.135.68.27

Threat-feed evidence

History

Related pages

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