Hostname
vectorlabs.com
Last fetched
vectorlabs.com resolves to 172.66.40.159, announced in 172.66.40.0/21 by CLOUDFLARENET - Cloudflare, Inc. in CA. vectorlabs.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
- 172.66.40.159
172.66.40.0/21 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.43.97
172.66.40.0/21 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1910
- Registrant organisation
- perfect privacy,
- Contact emails
- info@vectorlabs.com, mhlee@vectorlabs.com, pd8dh3b55j5@networksolutionsprivateregistration.com
Subdomains
Showing 12 of 35. View all subdomains →
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
- jillian.ns.cloudflare.com
- norm.ns.cloudflare.com
MX records
- d351866a.ess.barracudanetworks.com
- d351866b.ess.barracudanetworks.com
- vectorlabs-com.mail.protection.outlook.com
SPF policy
- include: spf.ess.barracudanetworks.com
- include: cust-spf.exacttarget.com
- include: _spf.psm.knowbe4.com
- include: spf.protection.outlook.com
- include: et._spf.pardot.com
- include: _spf.salesforce.com
- include: _spf1.mailgun.org
- include: _spf2.mailgun.org
- include: _spf.eu.mailgun.org
- ip: 104.21.83.152
- ip: 104.26.5.5
- ip: 12.131.170.66
- ip: 12.23.20.34
- ip: 144.208.64.33
- ip: 152.144.143.146
- ip: 172.67.177.218
- ip: 184.182.222.61
- ip: 199.16.39.54
- ip: 216.243.1.210
- ip: 38.135.35.7
- ip: 40.107.94.101
- ip: 50.175.28.218
- ip: 51.77.110.141
- ip: 65.140.160.226
- ip: 65.140.160.227
- ip: 70.103.116.52
- ip: 80.73.251.238
Threat-feed evidence
History
Related pages
Pivot from vectorlabs.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: "vectorlabs.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.