Skip to content

Hostname

goregrish.com

Last fetched

goregrish.com resolves to 104.21.71.173, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. goregrish.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 · goregrish.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/goregrish.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:2487
Registrant organisation
anonymize,
Contact emails
goregrish.com-1jer0zfid5c1k@anonymize.com, goregrish.com-1jyai6hpxfjg7@anonymize.com, goregrish.com-tol8d52wk9bl@anonymize.com, 3403f6362352465cb202556fe4e6dd8f.protect@whoisguard.com, 3b1394c5f13f4747825f1d255d742182.protect@whoisguard.com, 61b02c1c0c4e4f22975382bf208f9d0f.protect@whoisguard.com, 852224f1e81e4a8581212979b76142b5.protect@whoisguard.com, d9693b6783404b8189aadff365e5a956.protect@withheldforprivacy.com, info@domain-contact.org

Subdomains

Subdomain
demo.goregrish.com
www.goregrish.com

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

  • lia.ns.cloudflare.com
  • piotr.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

MX records

  • inbound-smtp.us-east-1.amazonaws.com

Threat-feed evidence

History

Related pages

Pivot from goregrish.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: "goregrish.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.