Skip to content

Hostname

ggcircuit.com

Last fetched

ggcircuit.com resolves to 151.101.130.132, announced in 151.101.128.0/22 by FASTLY - Fastly, Inc. in CA. ggcircuit.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 · ggcircuit.comRouting diversity1.5/10Peering density8.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/ggcircuit.com

Resolution chain

IPv6 resolution

No AAAA record for ggcircuit.com is recorded in WhisperGraph.

Attribution

Fastly

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:81
Registrant organisation
chris magee
Contact emails
103ac3decdca9a2f051c9626a2574476-56435805@contact.gandi.net, 5b7276ed151504387d78aefb8b23ab43-4099979@contact.gandi.net

Subdomains

Subdomain
blog.ggcircuit.com
centers.ggcircuit.com
corporate.ggcircuit.com
dev.ggcircuit.com
fortnite.ggcircuit.com
growth.ggcircuit.com
help.ggcircuit.com
helpdesk.ggcircuit.com
home.ggcircuit.com
homebeta.ggcircuit.com
newblog.ggcircuit.com
roadmap.ggcircuit.com

Showing 12 of 14. View all subdomains →

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

Sample outbound links

Mail and authentication

Nameservers

  • ns-158.awsdns-19.com
  • ns-837.awsdns-40.net
  • ns-1031.awsdns-00.org
  • ns-2013.awsdns-59.co.uk

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

  • include: amazonses.com
  • include: _spf.google.com
  • include: spf.mandrillapp.com
  • include: servers.mcsv.net
  • include: u18300618.wl119.sendgrid.net

Threat-feed evidence

History

Related pages

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