Skip to content

Hostname

knock.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
chicago comp. comm. consult co
Contact emails
********@*****.***, knock.com@domainsbyproxy.com, jim@knock.com, jimknock@wwa.com

Subdomains

Subdomain
agent-support.knock.com
apply.knock.com
auth.knock.com
backyard.knock.com
backyard2.knock.com
blog.knock.com
courtyard.knock.com
dev.knock.com
developer.knock.com
help.knock.com
it.knock.com
labs.knock.com

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

Sample outbound links

Mail and authentication

Nameservers

  • ns-167.awsdns-20.com
  • ns1.vercel-dns.com
  • ns-873.awsdns-45.net
  • ns-1241.awsdns-27.org
  • ns-1694.awsdns-19.co.uk

MX records

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

SPF policy

  • include: customeriomail.com
  • include: _spf.google.com
  • include: em9009.seismic.com

Threat-feed evidence

History

Related pages

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