Skip to content

Hostname

consistent.in

Last fetched

consistent.in resolves to 148.66.136.60, announced in 148.66.136.0/22 by AS-26496-GO-DADDY-COM-LLC - GoDaddy.com, LLC in SG. consistent.in 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 · consistent.inRouting diversity2.4/10Peering density5.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/consistent.in

Resolution chain

IPv6 resolution

Attribution

godaddy com

ORIGIN_AS

WHOIS identity

Registrar
iana:801217
Registrant organisation
consistent cloud
Contact emails
consistentcloud@gmail.com, webadmin@theagence.com

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

  • anita.ns.cloudflare.com
  • kolton.ns.cloudflare.com
  • dns1.bigrock.in
  • dns2.bigrock.in
  • dns3.bigrock.in
  • dns4.bigrock.in
  • 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
  • us2.mx1.mailhostbox.com
  • us2.mx2.mailhostbox.com
  • us2.mx3.mailhostbox.com

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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