Skip to content

Hostname

limabeads.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
steve@limabeads.com, nocontactsfound@secureserver.net

Subdomains

Subdomain
iga.limabeads.com
print.limabeads.com
s.limabeads.com
s1.limabeads.com
s2.limabeads.com
s3.limabeads.com
www.limabeads.com

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

  • ns-321.awsdns-40.com
  • ns-593.awsdns-10.net
  • ns-1156.awsdns-16.org
  • ns-1993.awsdns-57.co.uk

MX records

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

SPF policy

  • include: amazonses.com
  • include: cmail1.com
  • include: _spf.createsend.com
  • include: _spf.google.com
  • mx: limabeads.com
  • include: spf.zoho.com
  • include: transmail.net

Threat-feed evidence

History

Related pages

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