Skip to content

Hostname

omoda.de

Last fetched

omoda.de resolves to 85.10.159.162, announced in 85.10.159.0/24 by COMBELL-AS - Combell NV in NL. omoda.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 · omoda.deRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/omoda.de

Resolution chain

IPv6 resolution

Attribution

combell

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for omoda.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
development.omoda.de
new.omoda.de
preview-akamai.omoda.de
sst.omoda.de
staging.omoda.de
wildcard.omoda.de
www.omoda.de

Showing 7 of 7 subdomains (7 per page).

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

  • ns2.transip.eu
  • ns0.transip.net
  • ns1.transip.nl

MX records

  • omoda-de.mail.protection.outlook.com

SPF policy

  • ip: 62.21.139.208/29
  • a: submission.antispamcloud.com
  • include: spf.protection.outlook.com
  • include: trustpilotservice.com
  • include: mail.zendesk.com
  • mx: omoda.de
  • a: development-eu01-omodaschoenenbv.demandware.net
  • a: production.eu01.omodaschoenenbv.demandware.net
  • a: production-eu01-omodaschoenenbv.demandware.net
  • a: staging-eu01-omodaschoenenbv.demandware.net
  • include: _spf.afasonline.nl
  • ip: 13.94.197.16
  • ip: 141.138.199.164
  • ip: 213.206.116.28

Threat-feed evidence

History

Related pages

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