Skip to content

Hostname

granger.com

Last fetched

granger.com resolves to 104.21.52.116, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. granger.com 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 · granger.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/granger.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
b556t4n34fc@networksolutionsprivateregistration.com, d944e9gn94r@networksolutionsprivateregistration.com, dj8ab5f265w@networksolutionsprivateregistration.com, no.valid.email@worldnic.com, grangerinfo@granger.com, kq5xy7qm6qh@networksolutionsprivateregistration.com, mdejoux@granger.com, mj7ss4vu5g8@networksolutionsprivateregistration.com, rr89k9k96r8@networksolutionsprivateregistration.com, um6wq8sy4rp@networksolutionsprivateregistration.com, vz8vz4fd9vq@networksolutionsprivateregistration.com, xp7sd2wx6x7@networksolutionsprivateregistration.com, xv8477b44qk@networksolutionsprivateregistration.com

Subdomains

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

Mail and authentication

Nameservers

  • jessica.ns.cloudflare.com
  • peyton.ns.cloudflare.com
  • ns57.worldnic.com
  • ns58.worldnic.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx.3.googlemail.com
  • aspmx2.googlemail.com

SPF policy

  • include: _spf.google.com
  • ip: 216.47.170.75

Threat-feed evidence

History

Related pages

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