Skip to content

Hostname

inkbook.com

Last fetched

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

Resolution chain

Attribution

Aws

cloud · MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of inkbook.com owner
Contact emails
dev@daysmart.com, 1110926f-89a0-40a4-a9bd-8474a3ab1d8b@identity-protect.org, 2da08ecc-8df4-4f1e-afca-371475e9dc8d@identity-protect.org, 386c7b15-36bd-4c09-9ecd-e24844d96bb9@identity-protect.org, 42f982be-4119-4c24-be90-d1c9bf9dbf7d@identity-protect.org, 573ee44a-5ccf-48d3-a500-d73190f55063@identity-protect.org, 77c48000-e235-42ab-aba7-28e2028b97f2@identity-protect.org, owner-4104491@inkbook.com.whoisprivacyservice.org, owner-5192163@inkbook.com.whoisprivacyservice.org

Subdomains

Subdomain
account.inkbook.com
online.inkbook.com
reviews.inkbook.com
www.inkbook.com

Showing 4 of 4 subdomains (4 per page).

Mail and authentication

Nameservers

  • ns-87.awsdns-10.com
  • ns-870.awsdns-44.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-1725.awsdns-23.co.uk

MX records

  • inkbook.com

SPF policy

  • a: inkbook.com
  • mx: inkbook.com
  • ip: 198.1.121.173
  • ip: 66.147.244.236

Threat-feed evidence

History

Related pages

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