Skip to content

Hostname

woodwing.cloud

Last fetched

woodwing.cloud resolves to 13.227.146.115, announced in 13.227.146.0/23 by AMAZON-02 - Amazon.com, Inc. in PL. woodwing.cloud 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 · woodwing.cloudRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/woodwing.cloud

Resolution chain

IPv6 resolution

No AAAA record for woodwing.cloud is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1052
Registrant organisation
gerard van den akker
Contact emails
gak@woodwing.com, hosting@woodwing.com

Subdomains

Subdomain
_spf.woodwing.cloud
abe-test4.woodwing.cloud
andres-dev.woodwing.cloud
azmandev.woodwing.cloud
bauer.woodwing.cloud
bauer2.woodwing.cloud
ccs.woodwing.cloud
cops-dr.woodwing.cloud
cops.woodwing.cloud
dick-dev-01.woodwing.cloud
edb.woodwing.cloud
eos-au.woodwing.cloud

Showing 12 of 58. View all subdomains →

Mail and authentication

Nameservers

  • ns-440.awsdns-55.com
  • ns-801.awsdns-36.net
  • 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
  • ns-1114.awsdns-11.org
  • ns-1802.awsdns-33.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • ip: 62.21.242.24/28
  • a: woodwing.cloud
  • mx: woodwing.cloud
  • include: _spf.woodwing.cloud
  • include: amazonses.com
  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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