Hostname
mydaysstudio.com
Last fetched
mydaysstudio.com resolves to 1 IPv4 address operated by AS62904 - Eonix Corporation in US. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
mydaysstudio.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.140.12.164 | 104.140.12.0/22 | AS62904 | AS62904 - Eonix Corporation | US |
WHOIS identity
- Registrar
- iana:146
- Organization
- —
- Contact emails
- —
Subdomains
9 observed subdomains of mydaysstudio.com.
Threat posture
History
Mail and authentication
MX records
SPF policy
39 SPF mechanisms authorising senders for mydaysstudio.com.
| Mechanism | Target |
|---|---|
| SPF_A | mydaysstudio.com |
| SPF_IP | 102.129.240.129/32 |
| SPF_IP | 102.129.240.178/32 |
| SPF_IP | 102.129.240.208/32 |
| SPF_IP | 102.129.240.227/32 |
| SPF_IP | 102.129.240.240/32 |
| SPF_IP | 102.129.240.62/32 |
| SPF_IP | 102.129.240.72/32 |
| SPF_IP | 102.129.240.78/32 |
| SPF_IP | 104.206.56.43/32 |
| SPF_IP | 104.206.56.44/32 |
| SPF_IP | 147.79.0.208/32 |
| SPF_IP | 147.79.0.209/32 |
| SPF_IP | 172.99.150.202/32 |
| SPF_IP | 172.99.150.210/32 |
| SPF_IP | 172.99.150.215/32 |
| SPF_IP | 178.159.13.157/32 |
| SPF_IP | 178.159.13.163/32 |
| SPF_IP | 178.159.13.167/32 |
| SPF_IP | 178.159.13.173/32 |
| SPF_IP | 45.141.149.109/32 |
| SPF_IP | 45.141.149.143/32 |
| SPF_IP | 45.141.149.174/32 |
| SPF_IP | 45.141.149.21/32 |
| SPF_IP | 45.141.149.217/32 |
| SPF_IP | 45.141.149.248/32 |
| SPF_IP | 45.141.149.54/32 |
| SPF_IP | 45.141.149.71/32 |
| SPF_IP | 45.141.149.88/32 |
| SPF_IP | 45.141.149.9/32 |
| SPF_IP | 45.156.119.117/32 |
| SPF_IP | 45.156.119.17/32 |
| SPF_IP | 45.156.119.56/32 |
| SPF_IP | 45.156.119.84/32 |
| SPF_IP | 63.143.61.213/32 |
| SPF_IP | 63.143.61.214/32 |
| SPF_IP | 63.143.61.224/32 |
| SPF_IP | 63.143.61.225/32 |
| SPF_MX | mydaysstudio.com |
Related pages
Pivot deeper into the graph from mydaysstudio.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "mydaysstudio.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.