Skip to content

Hostname

paddleways.com

Last fetched

paddleways.com resolves to 108.138.26.17, announced in 108.138.24.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. paddleways.com 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 · paddleways.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/paddleways.com

Resolution chain

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:86
Registrant organisation
contact privacy inc. customer 0122166876
Contact emails
admin@domainassetholdings.com, paddleways.com@contactprivacy.com, kevin@paddleways.com, whois@emailaddressprotection.com

Subdomains

Subdomain
admin.paddleways.com
auth.paddleways.com
campaign-admin.paddleways.com
cf-staging.paddleways.com
clicks.paddleways.com
marketing-site.paddleways.com
river.paddleways.com
staging-api.paddleways.com
web3.paddleways.com
www.paddleways.com

Showing 10 of 10 subdomains (10 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

  • ns-44.awsdns-05.com
  • ns-764.awsdns-31.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-1298.awsdns-34.org
  • ns-1551.awsdns-01.co.uk

MX records

  • 3zvacvkn3brx3rcqbzowtcyyoui4rrk4a5xsp2pgnvhfakzgr5za.mx-verification.google.com
  • smtp.google.com

Threat-feed evidence

History

Related pages

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