Skip to content

Hostname

paddypartners.com

Last fetched

paddypartners.com resolves to 104.18.39.130, announced in 104.18.39.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. paddypartners.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 · paddypartners.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/paddypartners.com

Resolution chain

IPv6 resolution

No AAAA record for paddypartners.com is recorded in WhisperGraph.

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:447
Registrant organisation
domain manager
Contact emails
domains@paddypower.com, malaotopfbol@idp.email

Subdomains

Subdomain
admin.paddypartners.com
affiliates.paddypartners.com
www.paddypartners.com

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

  • dylan.ns.cloudflare.com
  • princess.ns.cloudflare.com

MX records

  • de-smtp-inbound-1.mimecast.com
  • de-smtp-inbound-2.mimecast.com

SPF policy

  • ip: 160.34.64.14/32
  • include: cust-spf.exacttarget.com
  • include: nets1.spf.messagelabs.com
  • include: nets2.spf.messagelabs.com
  • include: de._netblocks.mimecast.com
  • include: nw010.com
  • include: spf-a.rnmk.com
  • include: spf-b.rnmk.com
  • ip: 137.116.236.170
  • ip: 193.120.255.241
  • ip: 198.245.87.192
  • ip: 198.245.94.2
  • ip: 20.71.195.237
  • ip: 52.213.120.101
  • ip: 54.195.28.80
  • ip: 54.76.240.229

Threat-feed evidence

History

Related pages

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