Skip to content

Hostname

w2plus.de

Last fetched

w2plus.de resolves to 46.4.160.21, announced in 46.4.0.0/16 by HETZNER-AS - Hetzner Online GmbH in DE. w2plus.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 · w2plus.deRouting diversity1.5/10Peering density8.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/w2plus.de

Resolution chain

IPv6 resolution

Attribution

hetzner

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for w2plus.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
bitwarden.w2plus.de
checkmk.w2plus.de
cluster.w2plus.de
hetzner.w2plus.de
host185.w2plus.de
infoweb.w2plus.de
kerio.w2plus.de
nc.w2plus.de
omada.w2plus.de
smarthost02.w2plus.de
support.w2plus.de
tactical.w2plus.de

Showing 12 of 23. View all subdomains →

Mail and authentication

Nameservers

  • robotns3.second-ns.com
  • ns1.first-ns.de
  • robotns2.second-ns.de
  • 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

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

SPF policy

  • ip: 176.9.155.155/32
  • ip: 46.4.160.19/32
  • include: _spf.google.com
  • include: spf.protection.outlook.com
  • include: mail.zendesk.com
  • a: w2plus.de
  • a: mail1.sysda.net

Threat-feed evidence

History

Related pages

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