Skip to content

Hostname

locanto.de

Last fetched

locanto.de resolves to 104.18.41.65, announced in 104.18.41.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. locanto.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 · locanto.deRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/locanto.de

Resolution chain

IPv6 resolution

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

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for locanto.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
aachen.locanto.de
augsburg.locanto.de
baden-wuerttemberg.locanto.de
bamberg.locanto.de
bayern.locanto.de
bayreuth.locanto.de
berlin.locanto.de
bielefeld.locanto.de
bochum.locanto.de
bonn.locanto.de
bottrop.locanto.de
brandenburg-an-der-havel.locanto.de

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

Mail and authentication

Nameservers

  • cheryl.ns.cloudflare.com
  • phil.ns.cloudflare.com

MX records

  • mars.intermailgate.com

SPF policy

  • ip: 91.203.100.0/22
  • include: _spf.google.com
  • a: locanto.de
  • mx: locanto.de

Threat-feed evidence

History

Related pages

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