Hostname
perma-bound.com
Last fetched
perma-bound.com resolves to 104.20.46.210, announced in 104.20.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. perma-bound.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.20.46.210
104.20.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 12.170.195.93
12.128.0.0/9 · ATT-INTERNET4 - AT&T Enterprises, LLC · Jacksonville, US
- 172.66.147.72
172.66.144.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- perma-bound
- Contact emails
- hensonsw@perma-bound.com
Subdomains
| Subdomain |
|---|
| as2.perma-bound.com |
| clay.perma-bound.com |
| ftps.perma-bound.com |
| git.perma-bound.com |
| linode0.perma-bound.com |
| packages.perma-bound.com |
| pbtest.perma-bound.com |
| sftp.perma-bound.com |
| www.perma-bound.com |
Showing 9 of 9 subdomains (9 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
- doug.ns.cloudflare.com
- naya.ns.cloudflare.com
- dbru.br.ns.els-gms.att.net
- dmtu.mt.ns.els-gms.att.net
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
- perma-bound.com.s9a1.psmtp.com
- perma-bound.com.s9a2.psmtp.com
- perma-bound.com.s9b1.psmtp.com
- perma-bound.com.s9b2.psmtp.com
SPF policy
- ip: 74.125.148.0/22
- ip: 123.45.6.7/32
- include: _spf.google.com
Threat-feed evidence
History
Related pages
Pivot from perma-bound.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: "perma-bound.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.