Skip to content

Hostname

lotticards.de

Last fetched

lotticards.de resolves to 138.201.224.90, announced in 138.201.0.0/16 by HETZNER-AS - Hetzner Online GmbH in DE. lotticards.de 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 · lotticards.deRouting diversity1.5/10Peering density8.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/lotticards.de

Resolution chain

IPv6 resolution

No AAAA record for lotticards.de is recorded in WhisperGraph.

Attribution

hetzner

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for lotticards.de. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
autoconfig.lotticards.de
autodiscover.lotticards.de
aws.lotticards.de
blog.lotticards.de
do-not-reply.lotticards.de
easylisting.lotticards.de
mail.lotticards.de
newsletter.lotticards.de
webmail.lotticards.de
wildcard.lotticards.de
www.lotticards.de

Showing 11 of 12. 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

  • ns1.zitro.hosting
  • ns2.zitro.hosting
  • ns3.zitro.hosting
  • ns4.zitro.hosting

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: spf.crsend.com
  • include: _spf.google.com
  • a: lotticards.de
  • mx: lotticards.de
  • a: svr13.zitro.hosting
  • include: mailgun.org

Threat-feed evidence

History

Related pages

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