Skip to content

Hostname

greensec.de

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

hetzner

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for greensec.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
autoconfig.greensec.de
autoconfig3.greensec.de
billing-dev.greensec.de
billing.greensec.de
ca.greensec.de
census.greensec.de
checkip.greensec.de
customer.greensec.de
dataguard.greensec.de
debian.greensec.de
dmarc-view.greensec.de
docker.greensec.de

Showing 12 of 59. View all subdomains →

Mail and authentication

Nameservers

  • ns1.greensec.de
  • ns2.greensec.de
  • ns3.greensec.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

  • mx05.greensec.de

SPF policy

  • ip: 89.31.137.12/30
  • mx: greensec.de
  • a: a.spf.greensec.de
  • a: mail.netcup.net
  • ip: 2001:1b40:3601:6:0:0:ceca:de64
  • ip: 2001:470:1f15:ea4:0:0:0:1
  • ip: 2a01:4f8:221:13c3:1010:0:0:1
  • ip: 82.135.96.219

Threat-feed evidence

History

Related pages

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