Skip to content

Hostname

sentia.dk

Last fetched

sentia.dk resolves to 217.30.39.95, announced in 217.30.36.0/22 by SENTIA - Sentia Denmark A/S in DK. sentia.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 · sentia.dkRouting diversity2.4/10Peering density4.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.0/10canon.whisper.security/host/sentia.dk

Resolution chain

IPv6 resolution

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

Attribution

sentia denmark

ORIGIN_AS

WHOIS identity

Registrar
registrar:ascio technologies, corp. danmark - filial af ascio technologies, corp. canada
Registrant organisation
dhaenens jonas
Contact emails
dns@sentia.dk

Subdomains

Subdomain
api01.sentia.dk
automation.sentia.dk
aws-nginx-proxy.sentia.dk
ba.sentia.dk
cab-vmw-vc-p01.sentia.dk
cdn.sentia.dk
customerdb.sentia.dk
dev.sentia.dk
dghytten.sentia.dk
dns1.sentia.dk
dns2.sentia.dk
dns3.sentia.dk

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

  • ns.jay.net
  • ns2.jay.net
  • ns3.jay.net

MX records

  • sentia-dk.mail.protection.outlook.com

SPF policy

  • ip: 86.58.128.0/17
  • include: sentia.cloud
  • include: spf.protection.outlook.com
  • include: _spf.ipnordic.dk
  • include: spf.mailanyone.net
  • include: _netblocks.solido.net
  • ip: 149.72.53.54
  • ip: 217.30.38.2
  • ip: 217.30.38.251
  • ip: 217.30.38.65
  • ip: 31.31.83.1
  • ip: 77.66.19.24
  • ip: 81.19.233.100
  • ip: 86.48.50.55
  • ip: 89.188.85.26
  • ip: 91.193.138.202
  • ip: 91.215.163.52

Threat-feed evidence

History

Related pages

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