Hostname
ponpurelogistics.com
Last fetched
ponpurelogistics.com resolves to 104.21.30.6, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. ponpurelogistics.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.21.30.6
104.21.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.150.42
172.67.144.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- quadruple business services private limited.
- Contact emails
- thilak@quadrupleindia.com
Subdomains
| Subdomain |
|---|
| cs.ponpurelogistics.com |
| mail.ponpurelogistics.com |
| qr.ponpurelogistics.com |
| staging.ponpurelogistics.com |
| support.ponpurelogistics.com |
| tracking.ponpurelogistics.com |
| www.ponpurelogistics.com |
Showing 7 of 7 subdomains (7 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.
Mail and authentication
Nameservers
- kayden.ns.cloudflare.com
- romina.ns.cloudflare.com
MX records
- mx.zoho.in
- mx2.zoho.in
- mx3.zoho.in
- m4.pentabrains.tech
- m5.pentabrains.tech
SPF policy
- ip: 15.206.235.115/32
- ip: 140.86.75.192/32
- ip: 3.7.15.196/32
- ip: 140.86.75.78/32
- ip: 13.233.35.96/32
- include: email-messaging.com
- include: _spf.google.com
- include: spf.sendinblue.com
- include: zohomail.in
- ip: 51.254.145.171
Threat-feed evidence
History
Related pages
Pivot from ponpurelogistics.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: "ponpurelogistics.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.