Skip to content

Hostname

lordsbook.com

Last fetched

lordsbook.com resolves to 34.120.190.48, announced in 34.122.192.0/20 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. lordsbook.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 · lordsbook.comRouting diversity2.4/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.0/10canon.whisper.security/host/lordsbook.com

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:617
Registrant organisation
anonymize, llc.
Contact emails
lordsbook.com-1h7fusuz9ila0@anonymize.com, lordsbook.com-1iyhrekvf4pit@anonymize.com, lordsbook.com-rh5hsbbxurtt@anonymize.com, lordsbook.com-rhje547zxzqt@anonymize.com, lordsbook.com-s0uj8yu76913@anonymize.com, lordsbook.com-skpjwgrhofg6@anonymize.com, lordsbook.com-ure1kqg3q5o2@anonymize.com, lordsbook.com-vbkpxdr1ecma@anonymize.com, lordsbook.com-vf1fe2vnv9yv@anonymize.com, lordsbook.com-vf9r3fm2xx7l@anonymize.com, tdehaan1@aol.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • hydrogen.ns.hetzner.com
  • oxygen.ns.hetzner.com
  • ns1.himfirsthosting.com
  • ns2.himfirsthosting.com
  • helium.ns.hetzner.de
  • ns1.siteground.net
  • ns2.siteground.net

MX records

  • mail.lordsbook.com

SPF policy

  • a: lordsbook.com
  • mx: lordsbook.com

Threat-feed evidence

History

Related pages

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