Skip to content

Hostname

graymonk.com

Last fetched

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

Resolution chain

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:186
Registrant organisation
andrew peller
Contact emails
stevenheiss@graymonk.com

Subdomains

Subdomain
autodiscover.graymonk.com
fs1.graymonk.com
mail.graymonk.com
shop.graymonk.com
wineclub.graymonk.com
www.graymonk.com

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

Mail and authentication

Nameservers

  • kiki.ns.cloudflare.com
  • thomas.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

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

SPF policy

  • include: spf.ess.barracudanetworks.com
  • include: ca._netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • include: sendgrid.net
  • ip: 184.70.245.162
  • ip: 207.236.59.59
  • ip: 207.35.252.98
  • ip: 208.89.51.155
  • ip: 208.89.51.217
  • ip: 208.89.51.224
  • ip: 209.97.217.18
  • ip: 69.20.103.100

Threat-feed evidence

History

Related pages

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