Skip to content

Hostname

discussion.community

Last fetched

discussion.community resolves to 107.21.35.214, announced in 107.21.0.0/18 by AMAZON-AES - Amazon.com, Inc. in US. discussion.community 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 · discussion.communityRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/discussion.community

Resolution chain

IPv6 resolution

No AAAA record for discussion.community is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
website toolbox
Contact emails
support@websitetoolbox.com, do-not-use@privacy-protected.email, 05aa34515349c4e301fc2df1179e42af-28682492@contact.gandi.net

Subdomains

Subdomain
1hoursmarthome.discussion.community
21savagehactest.discussion.community
2hot4airwaves.discussion.community
9jacrew.discussion.community
abrasiveexpress.discussion.community
acestocktrader.discussion.community
acscomplaints.discussion.community
actiontreatment.discussion.community
activenorfolk.discussion.community
activetextbook.discussion.community
admc.discussion.community
adminmx5.discussion.community

Showing 12 of 436. View all subdomains →

Mail and authentication

Nameservers

  • ns-5.awsdns-00.com
  • ns-800.awsdns-36.net
  • 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
  • ns-1417.awsdns-49.org
  • ns-1703.awsdns-20.co.uk

MX records

  • smtp.google.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • a: mailers.websitetoolbox.com
  • a: discussion.community
  • mx: discussion.community

Threat-feed evidence

History

Related pages

Pivot from discussion.community 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: "discussion.community"})-[: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.