Skip to content

Hostname

rtad.gov.mm

Last fetched

rtad.gov.mm resolves to 103.89.48.96, announced in 103.89.48.0/24 by InformationTechnologyCyberSecurity-AS-AP - Dept. of Information Technology & Cyber Security in MM. rtad.gov.mm 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 · rtad.gov.mmRouting diversity2.4/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/rtad.gov.mm

Resolution chain

IPv6 resolution

No AAAA record for rtad.gov.mm is recorded in WhisperGraph.

Attribution

of information cyber security

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for rtad.gov.mm. 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.rtad.gov.mm
www.rtad.gov.mm

Showing 2 of 2 subdomains (2 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.

Sample inbound links

Mail and authentication

Nameservers

  • ns3.nic.net.mm
  • ns4.nic.net.mm
  • ns5.nic.net.mm
  • 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

  • rtad-gov-mm.mail.protection.outlook.com
  • ms38933023.msv1.invalid

SPF policy

  • include: spf.protection.outlook.com
  • a: rtad.gov.mm
  • mx: rtad.gov.mm
  • ip: 203.81.89.154

Threat-feed evidence

History

Related pages

Pivot from rtad.gov.mm 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: "rtad.gov.mm"})-[: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.