Skip to content

Hostname

techniklotsen.de

Last fetched

techniklotsen.de resolves to 185.181.132.197, announced in 185.181.132.0/22 by MITTWALD-AS - Robert Meyer trading as "Mittwald CM Service GmbH & Co. KG" in DE. techniklotsen.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 · techniklotsen.deRouting diversity1.5/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/techniklotsen.de

Resolution chain

IPv6 resolution

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

Attribution

robert meyer trading mittwald cm

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for techniklotsen.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
001vpn.techniklotsen.de
cp106.techniklotsen.de
lisa2.techniklotsen.de
lmc.techniklotsen.de
mdm.techniklotsen.de
mds.techniklotsen.de
meet.techniklotsen.de
mx1.techniklotsen.de
mx2.techniklotsen.de
mx3.techniklotsen.de
newsletter.techniklotsen.de
vpn.techniklotsen.de

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

  • ns01.versatel.de
  • ns02.versatel.de
  • ns04.versatel.de

MX records

  • mx1.techniklotsen.de
  • mx2.techniklotsen.de
  • mx3.techniklotsen.de

SPF policy

  • mx: techniklotsen.de
  • ip: 51.195.38.178

Threat-feed evidence

History

Related pages

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