Skip to content

Hostname

tdgarden.com

Last fetched

tdgarden.com resolves to 52.4.54.3, announced in 52.4.0.0/14 by AMAZON-AES - Amazon.com, Inc. in US. tdgarden.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 · tdgarden.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/tdgarden.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
delaware north companies
Contact emails
digitalmarketing@delawarenorth.com, mmccormick@delawarenorth.com, sszeglow@delawarenorth.com, sszeglow@dncinc.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns59.worldnic.com
  • ns60.worldnic.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

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

SPF policy

  • ip: 52.40.214.53/32
  • ip: 209.47.1.69/32
  • include: spf.givex.com
  • include: us._netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • include: _spf.salesforce.com
  • ip: 129.145.16.238
  • ip: 129.145.16.239
  • ip: 129.145.16.240
  • ip: 198.183.184.42
  • ip: 198.183.184.44
  • ip: 216.57.137.171

Threat-feed evidence

History

Related pages

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