Skip to content

Hostname

goldenscent.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:83
Registrant organisation
aram gulf
Contact emails
info@aramgulf.com, malik.shehab@aramgulf.com, dataprivacyprotected@1und1.de, dataprivacyprotected@ionos.de

Subdomains

Subdomain
admin.goldenscent.com
ae-sandbox.goldenscent.com
ae.goldenscent.com
assets.goldenscent.com
bh.goldenscent.com
careers.goldenscent.com
dev-ae.goldenscent.com
dev-frontend.goldenscent.com
dev-global.goldenscent.com
dev-sa.goldenscent.com
dev.goldenscent.com
e.goldenscent.com

Showing 12 of 46. 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

Mail and authentication

Nameservers

  • ns-114.awsdns-14.com
  • ns-673.awsdns-20.net
  • ns-1297.awsdns-34.org
  • ns-2039.awsdns-62.co.uk

MX records

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

SPF policy

  • include: em3815.goldenscent.com
  • include: _spf.google.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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