Skip to content

Hostname

puzzlepassion.com

Last fetched

puzzlepassion.com resolves to 104.21.74.249, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. puzzlepassion.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 · puzzlepassion.comRouting diversity3.0/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/puzzlepassion.com

Resolution chain

IPv6 resolution

Attribution

grupo loading

ORIGIN_AS

WHOIS identity

Registrar
iana:379
Registrant organisation
identity protection shield
Contact emails
whoiscontact@domainconnection.info, 1312171324252wn295589r@whois-privacy-service.net, 150817044425if295589r@whois-privacy-service.net, 2209160263123kq295589r@whois-privacy-service.net, 906172112760kl295589r@whois-privacy-service.net

Subdomains

Subdomain
backoffice.puzzlepassion.com
blog.puzzlepassion.com
www.puzzlepassion.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

  • love.ns.cloudflare.com
  • troy.ns.cloudflare.com
  • dns10.servidoresdns.net
  • dns9.servidoresdns.net

MX records

  • puzzlepassion-com.mail.protection.outlook.com

SPF policy

  • ip: 82.223.190.0/24
  • ip: 82.223.191.0/24
  • include: spf.protection.outlook.com
  • ip: 195.76.40.202
  • ip: 212.163.66.66
  • ip: 212.163.66.67
  • ip: 212.163.66.68
  • ip: 212.163.66.69
  • ip: 212.163.66.70
  • ip: 212.163.66.71
  • ip: 212.163.66.72
  • ip: 217.61.208.52
  • ip: 35.180.3.134
  • ip: 80.94.0.162
  • ip: 80.94.6.186

Threat-feed evidence

History

Related pages

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