Hostname
matandi.com
Last fetched
matandi.com resolves to 2 IPv4 addresses operated by AS15817 in DE. WHOIS lists iana:976 as the registrar.
Nutrition Label
Resolution chain
matandi.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 |
|---|---|---|---|---|
| 185.166.23.191 | 185.166.20.0/22 | AS15817 | — | DE |
| 216.162.200.200 | 216.162.200.0/24 | AS396982 | GOOGLE-CLOUD-PLATFORM - Google LLC | DE |
WHOIS identity
- Registrar
- iana:976
- Organization
- mike menke
- Contact emails
- i54z6aarihtcy37refyrmbjxn77o4nfej65ifl4ir5y3o@protectedmx.com
- i6jyqdfq5yc5jukpkds7hwtpjks5zkgt7ceq6h6yohdoq@protectedmx.com
- ibwvrxr72s2rmtug65xhlca6zsysxb4lzeezyfuazucvm@protectedmx.com
- ie7tjfbf33nrjm5xzut7i7ygpm2e66zh2z4hi2gqfzc7g@protectedmx.com
- ign42bb5dci57wseotvzu45hanawzmypfkyeoa3qc3v54@protectedmx.com
- iqcoyajdb2tn5fler7hev4t33q2eba4cx6man3gi6py7e@protectedmx.com
- irux3ferxhk46oud6l3toaq44kkmy5gej7xqg2ry5ecf6@protectedmx.com
- itbrl5xq744i5wu3mf7zqf2mw2zqooylgcylw5fanawsa@protectedmx.com
- ivowg4s2mq63m3jsbtsck7df3gysxjlfh7cdyoeyxkpqw@protectedmx.com
- mike@menke.tv
Subdomains
19 observed subdomains of matandi.com.
Web-graph footprint
Distinct hostnames that link to or from matandi.com in the public web crawl.
1 site linked to from this hostname.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
1 SPF mechanism authorising senders for matandi.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | spf.protection.outlook.com |
Related pages
Pivot deeper into the graph from matandi.com.
- IP · 185.166.23.191
- ASN · AS15817
- Registrar · iana:976
- Country · DE
- Email · i54z6aarihtcy37refyrmbjxn77o4nfej65ifl4ir5y3o@protectedmx.com
- TLD · .com
- Browse hostnames · ma…
- 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: "matandi.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.