Skip to content

Hostname

werktuigen.com

Last fetched

werktuigen.com resolves to 193.142.41.60, announced in 193.142.41.0/24 by IP-PROJECTS - Michael Sebastian Schinzel trading as IP-Projects GmbH & Co. KG in DE. werktuigen.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 · werktuigen.comRouting diversity2.4/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.0/10canon.whisper.security/host/werktuigen.com

Resolution chain

IPv6 resolution

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

Attribution

michael sebastian schinzel trading ip projects

ORIGIN_AS

WHOIS identity

Registrar
iana:976
Registrant organisation
j.c. nell
Contact emails
i6g7zlpny2apw63enwmkzxfp4oj7d53dytos2vtqgrqh6@protectedmx.com, iazcbkbekp7g3idmtzvuynekgmgaoocljpk2uhdq7p2yc@protectedmx.com, ib64jlyxlctxojpmmj4cd436pxtyc3hgmvr337nyafjfe@protectedmx.com, icf7jfq5d6lej7cxukhtijsaujpumgudqr7oaegq6eykm@protectedmx.com, ii2o7lmhdri6vsv3paysqc3e5prengl6kfgqa6nixxu4m@protectedmx.com, ik3mc4fzfkfyznsufhdxkdgojmql2jxqhjvp7epa4k6hs@protectedmx.com, imh462t5no5gaoyett4cdzgzz75qyq5a42bdxblqhitgc@protectedmx.com, imtqpshctumvszkguyvvynkwzasbxqg3dcggnjniuyh2u@protectedmx.com, jcnell@planet.nl

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • pns41.cloudns.net
  • pns42.cloudns.net
  • pns43.cloudns.net
  • pns44.cloudns.net
  • ns1.routing.net
  • ns2.routing.net
  • ns3.routing.net

MX records

  • werktuigen-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • mx: werktuigen.com

Threat-feed evidence

History

Related pages

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