Skip to content

Hostname

thegoring.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1390
Registrant organisation
david morgan-hewitt
Contact emails
davidm-h@thegoring.com, richard@hartsathome.co.uk

Subdomains

Subdomain
authorisations.thegoring.com
book.thegoring.com
wildcard.thegoring.com
www.thegoring.com

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

Sample outbound links

Mail and authentication

Nameservers

  • bethany.ns.cloudflare.com
  • kareem.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

  • eu-smtp-inbound-1.mimecast.com
  • eu-smtp-inbound-2.mimecast.com

SPF policy

  • include: _spf.createsend.com
  • include: emailsrvr.com
  • include: eu._netblocks.mimecast.com
  • include: oracleindustry.com
  • include: spf.protection.outlook.com
  • include: theaccessgroupspf.smtp.com
  • include: spf.synxis.com
  • mx: thegoring.com

Threat-feed evidence

History

Related pages

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