Skip to content

Hostname

danburymint.com

Last fetched

danburymint.com resolves to 52.66.101.246, announced in 52.66.64.0/18 by AMAZON-02 - Amazon.com, Inc. in IN. danburymint.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 · danburymint.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/danburymint.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
mbi
Contact emails
networkmanager@mbi-inc.com, tmastro@mbi-inc.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

  • a.gtld-servers.net
  • b.gtld-servers.net
  • c.gtld-servers.net
  • d.gtld-servers.net
  • e.gtld-servers.net
  • f.gtld-servers.net
  • g.gtld-servers.net
  • h.gtld-servers.net
  • i.gtld-servers.net
  • j.gtld-servers.net
  • k.gtld-servers.net
  • l.gtld-servers.net
  • m.gtld-servers.net
  • dns1.p02.nsone.net
  • dns2.p02.nsone.net
  • dns3.p02.nsone.net
  • dns4.p02.nsone.net

MX records

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

SPF policy

  • include: cust-spf.exacttarget.com
  • include: us._netblocks.mimecast.com
  • include: _spf.salesforce.com
  • a: production.na01.mbi.demandware.net
  • a: outgoing.pod281.demandware.net
  • ip: 128.17.1.170
  • ip: 128.17.1.173
  • ip: 136.146.4.218
  • ip: 136.147.142.237
  • ip: 66.231.84.146

Threat-feed evidence

History

Related pages

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