Hostname
preciso.net
Last fetched
preciso.net resolves to 104.18.0.2, announced in 104.18.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. preciso.net 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.18.0.2
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.1.2
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.21.78.120
104.21.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.21.82.71
104.21.80.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.197.189
172.67.192.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.220.246
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- china capital investment
- Contact emails
- admin@newvcorp.com, info@chinacapital.com, privacy@dynadot.com
Subdomains
| Subdomain |
|---|
| apijob.preciso.net |
| app1.preciso.net |
| apppartner.preciso.net |
| appsmagentogamma.preciso.net |
| beta-appshopify.preciso.net |
| cdn.preciso.net |
| mail.preciso.net |
| precisolite.preciso.net |
| www.preciso.net |
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.
Sample inbound links
Mail and authentication
Nameservers
- coleman.ns.cloudflare.com
- ethan.ns.cloudflare.com
- walk.ns.cloudflare.com
- zita.ns.cloudflare.com
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
SPF policy
- include: _spf.mailspamprotection.com
- a: preciso.net
- mx: preciso.net
- a: ns1.c62872.sgvps.net
Threat-feed evidence
History
Related pages
Pivot from preciso.net 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: "preciso.net"})-[: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.