Skip to content

Hostname

goldcore.com

Last fetched

goldcore.com resolves to 108.157.238.16, announced in 108.157.238.0/23 by AMAZON-02 - Amazon.com, Inc. in IN. goldcore.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 · goldcore.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/goldcore.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:113
Registrant organisation
goldcore
Contact emails
stephen.flood@goldcore.ie

Subdomains

Subdomain
affiliates.goldcore.com
api.goldcore.com
blog.goldcore.com
broadcast.goldcore.com
chat.goldcore.com
info.goldcore.com
mockups.goldcore.com
myaccount.goldcore.com
news.goldcore.com
pilot-newos-news.goldcore.com
pilot-scontrols.goldcore.com
pilot-v4.goldcore.com

Showing 12 of 25. 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-373.awsdns-46.com
  • ns-714.awsdns-25.net
  • ns-1417.awsdns-49.org
  • ns-1581.awsdns-05.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com

SPF policy

  • mx: goldcore.com
  • include: _spf.google.com
  • include: _spf.salesforce.com
  • include: 233034.spf03.hubspotemail.net

Threat-feed evidence

History

Related pages

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