Skip to content

Hostname

tecsys.dk

Last fetched

tecsys.dk resolves to 35.214.171.82, announced in 35.214.128.0/17 by GOOGLE-2 - Google LLC in NL. tecsys.dk 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 · tecsys.dkRouting diversity1.5/10Peering density5.3/10MOAS conflict⚠ 2 conflictsThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/tecsys.dk

Resolution chain

IPv6 resolution

No AAAA record for tecsys.dk is recorded in WhisperGraph.

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
tecsys a/s
Contact emails
jorgen.frederiksen@tecsys.com

Subdomains

Subdomain
_spf.tecsys.dk
ackro.tecsys.dk
bibs.tecsys.dk
bioroute.tecsys.dk
candock.tecsys.dk
daros.tecsys.dk
distribute.tecsys.dk
hofor.tecsys.dk
http-wms-in-content-non_secure.tecsys.dk
mobicert.tecsys.dk
nat.tecsys.dk
norge.tecsys.dk

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

  • ns1.pcsys.dk
  • ns2.pcsys.dk
  • ns3.pcsys.dk
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • dk.mx1.mailanyone.net
  • dk.mx3.mailanyone.net
  • dk.mx2.mx25.net
  • dk.mx4.mx25.net

SPF policy

  • ip: 193.186.35.0/24
  • ip: 62.116.202.160/27
  • ip: 152.115.42.192/27
  • ip: 86.58.175.32/27
  • include: emsd1.com
  • include: spf.mailanyone.net
  • include: servers.mcsv.net
  • ip: 52.232.29.95
  • ip: 89.221.169.42

Threat-feed evidence

History

Related pages

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