Hostname
necando.com
Last fetched
necando.com resolves to 1 IPv4 address operated by GOOGLE-CLOUD-PLATFORM - Google LLC in US. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
necando.com resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.196.222.91 | 104.196.208.0/20 | AS396982 | GOOGLE-CLOUD-PLATFORM - Google LLC | US |
WHOIS identity
- Registrar
- iana:146
- Organization
- domains by proxy,
- Contact emails
Subdomains
8 observed subdomains of necando.com.
Web-graph footprint
Distinct hostnames that link to or from necando.com in the public web crawl.
Sample inbound links
Sample outbound links
- formation-i2-analysts-notebook-anb1-20260112.eventbrite.ca
- formation-i2-ibase-designer-20251125.eventbrite.ca
- i2-analysts-notebook-training-anb1-202501201.eventbrite.ca
- i2-analysts-notebook-training-part-1-anb1-20260126.eventbrite.ca
- i2-ibase-designer-training-ibd-20251217.eventbrite.ca
- i2-ibase-user-training-iba-20251118.eventbrite.ca
- i2-ibase-user-training-iba-20260216.eventbrite.ca
- lunch-decouverte-cyber-resilience-20251106.eventbrite.ca
- cai.gouv.qc.ca
- legisquebec.gouv.qc.ca
Threat posture
History
Mail and authentication
MX records
SPF policy
5 SPF mechanisms authorising senders for necando.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.notes.na.collabserv.com |
| SPF_INCLUDE | aspmx.pardot.com |
| SPF_INCLUDE | onyx2.webcorelabs.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_INCLUDE | spf1.necando.com |
Related pages
Pivot deeper into the graph from necando.com.
- IP · 104.196.222.91
- ASN · AS396982GOOGLE-CLOUD-PLATFORM - Google LLC
- Registrar · iana:146
- Country · US
- Email · psalois@necando.com
- TLD · .com
- Browse hostnames · ne…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "necando.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.