Hostname
vince.com
Last fetched
vince.com resolves to 104.16.30.109, announced in 104.17.192.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. vince.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.16.30.109
104.17.192.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.16.67.104
104.17.240.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for vince.com is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
- Contact emails
- vince.com@domainsbyproxy.com
Subdomains
| Subdomain |
|---|
| daeez.vince.com |
| dev.vince.com |
| development.vince.com |
| enews.vince.com |
| investors.vince.com |
| m.vince.com |
| smetrics.vince.com |
| staging.vince.com |
| t.vince.com |
| vinceservices.vince.com |
| wd.vince.com |
| www.vince.com |
Showing 12 of 12 subdomains (12 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
- pdns77.ultradns.biz
- ns10.dnsmadeeasy.com
- ns11.dnsmadeeasy.com
- ns12.dnsmadeeasy.com
- ns13.dnsmadeeasy.com
- ns14.dnsmadeeasy.com
- ns15.dnsmadeeasy.com
- pdns77.ultradns.com
- pdns77.ultradns.net
MX records
- vince-com.mail.protection.outlook.com
SPF policy
- include: spf.mandrillapp.com
- include: spf.protection.outlook.com
- include: _spf.salesforce.com
- a: production-na02-vince.demandware.net
- a: production.na02.vince.demandware.net
- a: production.web.vince.demandware.net
- ip: 104.41.152.44
- ip: 207.140.37.170
- ip: 207.140.37.3
- ip: 212.25.239.10
- ip: 40.71.20.210
- ip: 40.75.91.123
- ip: 52.188.123.132
Threat-feed evidence
History
Related pages
Pivot from vince.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: "vince.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.