Hostname
evondos.com
Last fetched
evondos.com resolves to 2 IPv4 addresses operated by CLOUDFLARESPECTRUM Cloudflare, Inc. in US. WHOIS lists iana:113 as the registrar.
Nutrition Label
Resolution chain
evondos.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 199.60.103.105 | 199.60.103.0/24 | AS209242 | CLOUDFLARESPECTRUM Cloudflare, Inc. | US |
| 199.60.103.5 | 199.60.103.0/24 | AS209242 | CLOUDFLARESPECTRUM Cloudflare, Inc. | US |
WHOIS identity
- Registrar
- iana:113
- Organization
- evondos oy
- Contact emails
Subdomains
15 observed subdomains of evondos.com.
Web-graph footprint
Distinct hostnames that link to or from evondos.com in the public web crawl.
58 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
15 SPF mechanisms authorising senders for evondos.com.
| Mechanism | Target |
|---|---|
| SPF_A | postiturvamx1.lounea.fi |
| SPF_A | postiturvamx2.lounea.fi |
| SPF_INCLUDE | 25504804.spf04.hubspotemail.net |
| SPF_INCLUDE | _spf.salesforce.com |
| SPF_INCLUDE | spf.evondos.com |
| SPF_INCLUDE | spf.ficolo.net |
| SPF_INCLUDE | spf.lianamailer.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_INCLUDE | spf.protection.vine.eu |
| SPF_IP | 185.40.56.78 |
| SPF_IP | 185.85.210.246 |
| SPF_IP | 194.240.181.58 |
| SPF_IP | 62.197.191.202 |
| SPF_IP | 91.237.151.27/32 |
| SPF_MX | evondos.com |
Related pages
Pivot deeper into the graph from evondos.com.
- IP · 199.60.103.105
- ASN · AS209242CLOUDFLARESPECTRUM Cloudflare, Inc.
- Registrar · iana:113
- Country · US
- Email · mirva.ylosmaki@evondos.com
- TLD · .com
- Browse hostnames · ev…
- 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: "evondos.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.