Skip to content

Hostname

rigov.org

Last fetched

rigov.org resolves to 208.90.188.146, announced in 208.90.188.0/22 by NETSOLUS-NETWORKS - IP Pathways, LLC in US. rigov.org 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 · rigov.orgRouting diversity1.5/10Peering density2.4/10MOAS conflict⚠ 1 conflictThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/rigov.org

Resolution chain

IPv6 resolution

No AAAA record for rigov.org is recorded in WhisperGraph.

Attribution

ip pathways

ORIGIN_AS

WHOIS identity

Registrar
iana:9
Registrant organisation
city of rock island
Contact emails
bain.timothy@rigov.org

Subdomains

Subdomain
intra.rigov.org
intranet.rigov.org
mobility.rigov.org
sma.rigov.org
www.rigov.org
www2.rigov.org
www3.rigov.org

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

  • ns1.dnsbycomodo.net
  • ns2.dnsbycomodo.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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • ip: 216.175.22.128/27
  • include: email.active.com
  • include: spf.constantcontact.com
  • include: _spf.google.com
  • ip: 63.142.45.34

Threat-feed evidence

History

Related pages

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