Skip to content

Hostname

letsloop.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
site admin
Contact emails
308fb34a52ea9c7368c8394ca8b6fa2d-1186450@contact.gandi.net, 3720d8123ac1cb742e0ace40e3372d7d-1186450@contact.gandi.net, 5ff7c54365a55858f6993d4262d670cd-1186450@contact.gandi.net

Subdomains

Subdomain
blog.letsloop.com
newmail.letsloop.com
www.letsloop.com

Showing 3 of 3 subdomains (3 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-404.awsdns-50.com
  • ns-577.awsdns-08.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-1244.awsdns-27.org
  • ns-1851.awsdns-39.co.uk

MX records

  • mail.protonmail.ch
  • mailsec.protonmail.ch

SPF policy

  • include: _spf.protonmail.ch

Threat-feed evidence

History

Related pages

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