Skip to content

Hostname

lazycatsoftware.com

Last fetched

lazycatsoftware.com resolves to 81.171.24.23, announced in 81.171.92.0/23 by LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. in NL. lazycatsoftware.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 · lazycatsoftware.comRouting diversity1.5/10Peering density3.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/lazycatsoftware.com

Resolution chain

IPv6 resolution

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

Attribution

leaseweb nl ams netherlands

ORIGIN_AS

WHOIS identity

Registrar
iana:303
Registrant organisation
domain admin
Contact emails
lazycatsoftware.com@whoisprotectservice.net, contact@privacyprotect.org

Subdomains

Subdomain
mail.lazycatsoftware.com
ns1.lazycatsoftware.com
ns2.lazycatsoftware.com
www.lazycatsoftware.com

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

  • ns1.lazycatsoftware.com
  • ns2.lazycatsoftware.com
  • 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
  • ns1.domain.tld

MX records

  • mail.lazycatsoftware.com

SPF policy

  • a: lazycatsoftware.com
  • mx: lazycatsoftware.com
  • ip: 81.171.24.23

Threat-feed evidence

History

Related pages

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