Skip to content

Hostname

notebookreview.com

Last fetched

notebookreview.com resolves to 34.120.117.196, announced in 34.120.0.0/14 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. notebookreview.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 · notebookreview.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/notebookreview.com

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:291
Registrant organisation
hostmaster hostmaster
Contact emails
notebookreview.com-registrant@directnicwhoiscompliance.com, hostmaster@techtarget.com, notebookreview.com@dnic.jewellaprivacy.com

Subdomains

Subdomain
consent-qa.notebookreview.com
consent.notebookreview.com
forum.notebookreview.com
users.notebookreview.com
www.notebookreview.com

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

Sample outbound links

Mail and authentication

Nameservers

  • ns10.techtarget.com
  • ns11.techtarget.com
  • ns12.techtarget.com
  • ns13.techtarget.com
  • ns14.techtarget.com
  • ns15.techtarget.com

MX records

  • mx0a-00051b01.pphosted.com
  • mx0b-00051b01.pphosted.com

SPF policy

  • include: docebosaas.com
  • include: relays.gooddata.com
  • include: mktomail.com
  • include: spf.protection.outlook.com
  • include: spf-00051b01.pphosted.com
  • include: _spf.salesforce.com
  • include: clientspf.zestbenefits.com
  • ip: 208.84.65.49
  • ip: 67.231.152.14

Threat-feed evidence

History

Related pages

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