Skip to content

Hostname

royalgreen.net

Last fetched

royalgreen.net resolves to 123.136.31.6, announced in 123.136.31.0/24 by ROYALGREENINCBD-TRANSIT-AS-AP - Royal Green Communication Limited in BD. royalgreen.net 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 · royalgreen.netRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/royalgreen.net

Resolution chain

IPv6 resolution

No AAAA record for royalgreen.net is recorded in WhisperGraph.

Attribution

royal green

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
azizul haque
Contact emails
royalgreeninc@yahoo.com, zia@royalgreen.net

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • guss.ns.cloudflare.com
  • meiling.ns.cloudflare.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.royalgreen.net
  • ns2.royalgreen.net

MX records

  • mail.royalgreen.net
  • pmg.royalgreen.net
  • spam.royalgreen.net

SPF policy

  • ip: 123.136.31.0/28
  • ip: 123.136.31.10/32
  • ip: 123.136.29.18/32
  • a: royalgreen.net
  • mx: royalgreen.net

Threat-feed evidence

History

Related pages

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