Skip to content

Hostname

lamoda.pl

Last fetched

lamoda.pl resolves to 13.225.103.127, announced in 13.225.96.0/21 by AMAZON-02 - Amazon.com, Inc. in IN. lamoda.pl 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 · lamoda.plRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/lamoda.pl

Resolution chain

IPv6 resolution

No AAAA record for lamoda.pl is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
registrar:cyber_folks s.a.
Registrant organisation
ringier axel springer polska sp. z o.o.

Subdomains

Subdomain
blog.lamoda.pl
dcc.lamoda.pl
dysk.lamoda.pl
git.lamoda.pl
klik.lamoda.pl
monitoring.lamoda.pl
nalm.lamoda.pl
newsletter.lamoda.pl
panel.lamoda.pl
secure.lamoda.pl
stage.lamoda.pl
static.lamoda.pl

Showing 12 of 18. View all subdomains →

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

  • ns73.ringpublishing.net
  • ns74.ringpublishing.net
  • ns75.ringpublishing.net
  • ns76.ringpublishing.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

MX records

  • lamoda-pl.mail.protection.outlook.com

SPF policy

  • include: dreamlab.pl
  • include: _spf.jupiter.salesmanago.pl

Threat-feed evidence

History

Related pages

Pivot from lamoda.pl 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: "lamoda.pl"})-[: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.