Skip to content

Hostname

puwell.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of puwell.com owner
Contact emails
ykhe@sina.com.cn, 0b207e57-f163-4e50-986d-b250ba220fcd@identity-protect.org, 2f9d5631-782d-4a8d-b454-e3337dc2f988@identity-protect.org, 319fa8ec-ce04-43bc-9cd0-fd1e05f961be@identity-protect.org, 32f6b08c-5ea8-4cad-9636-df76e9a53680@identity-protect.org, c18d6710-2c76-4839-bb7c-02d4f8d43b3e@identity-protect.org, c97e53c9-e2e7-4923-b4ad-9512a8c45c67@identity-protect.org

Subdomains

Subdomain
apaytest.puwell.com
autoconfig.puwell.com
open.puwell.com
paycn.puwell.com
payen.puwell.com
support.puwell.com
www.puwell.com

Showing 7 of 7 subdomains (7 per page).

Mail and authentication

Nameservers

  • ns-387.awsdns-48.com
  • ns-780.awsdns-33.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-1393.awsdns-46.org
  • ns-2007.awsdns-58.co.uk

MX records

  • mxbiz1.qq.com
  • mxbiz2.qq.com
  • mail.flowwoo.com

SPF policy

  • include: spf.mail.qq.com

Threat-feed evidence

History

Related pages

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