Skip to content

Hostname

tmecosys.net

Last fetched

tmecosys.net resolves to 3.66.70.133, announced in 3.64.0.0/12 by AMAZON-02 - Amazon.com, Inc. in DE. tmecosys.net 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 · tmecosys.netRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.2/10canon.whisper.security/host/tmecosys.net

Resolution chain

IPv6 resolution

No AAAA record for tmecosys.net is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:976
Registrant organisation
julius ganns
Contact emails
julius.ganns@vorwerk.ch, i3kl6ue3v2qrocuqyisnk3tdfwhbce7mrowouxlysom6c@protectedmx.com, i5qtgkkeduxftyrufdq4452rsrh62ita4jtjpjjafriza@protectedmx.com, ianftirbnckiphpez5jn7igkcavba4ol5v6xncsiyxv72@protectedmx.com, ico5dhu7ucqy7dvqsgdpjbmbjrwgguqxsffxecba4xksa@protectedmx.com, iegybpmnoz42ll3rl3ng6sviuwtb3oshx5podw3qy6khe@protectedmx.com, ihyd3jkpqsil7nwoiutm6hxuemwgjvauhi2oleaykxrve@protectedmx.com, iigg7dd3pqffzdjkpahjvnnvfm37mfb6owl5qugacqft4@protectedmx.com, ionoxad23dpag5niencswj6akl6relakalm6bjlqeqk3m@protectedmx.com, izret6g5gdvy4ltlbktwsizlli3bngtd5hs6vetapmfpa@protectedmx.com, michael.kabilka@vorwerk.de

Subdomains

Mail and authentication

Nameservers

  • ns-361.awsdns-45.com
  • ns-362.awsdns-45.com
  • ns-834.awsdns-40.net
  • ns-1388.awsdns-45.org
  • ns-2031.awsdns-61.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com
  • ms12548338.msv1.invalid.outlook.com

Threat-feed evidence

History

Related pages

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