Skip to content

Hostname

padel-point.de

Last fetched

padel-point.de resolves to 104.26.0.43, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. padel-point.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 · padel-point.deRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.2/10canon.whisper.security/host/padel-point.de

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for padel-point.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
blog.padel-point.de
click.padel-point.de
development.padel-point.de
link.padel-point.de
sgtm.padel-point.de
shop.padel-point.de
www.padel-point.de

Showing 7 of 8. View all subdomains →

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

  • diva.ns.cloudflare.com
  • rick.ns.cloudflare.com
  • ns.udag.de
  • ns.udag.net
  • ns.udag.org

MX records

  • padelpoint-de01c.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • mx: padel-point.de
  • include: www.padel-point.de
  • include: tennis-point.de
  • a: production.eu01.tennispoint.demandware.net

Threat-feed evidence

History

Related pages

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