Hostname
maletis.com
Last fetched
maletis.com resolves to 2 IPv4 addresses operated by AKAMAI-LINODE-AP Akamai Connected Cloud in US. WHOIS lists iana:2 as the registrar.
Nutrition Label
Resolution chain
maletis.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 |
|---|---|---|---|---|
| 172.232.164.221 | 172.232.160.0/19 | AS63949 | AKAMAI-LINODE-AP Akamai Connected Cloud | US |
| 45.33.51.49 | 45.33.32.0/19 | AS63949 | AKAMAI-LINODE-AP Akamai Connected Cloud | US |
WHOIS identity
- Registrar
- iana:2
- Organization
- perfect privacy,
- Contact emails
- dh3x837b2t7@networksolutionsprivateregistration.com
- dq4mj75x8xn@networksolutionsprivateregistration.com
- fv6bp4nb2pc@networksolutionsprivateregistration.com
- nq24s2ky6dk@networksolutionsprivateregistration.com
- py8rc5j43sm@networksolutionsprivateregistration.com
- qv2mb25g8yp@networksolutionsprivateregistration.com
- vv5r62gs464@networksolutionsprivateregistration.com
- xv4gu89y5gv@networksolutionsprivateregistration.com
- ys4j23a84qa@networksolutionsprivateregistration.com
Subdomains
6 observed subdomains of maletis.com.
Web-graph footprint
Distinct hostnames that link to or from maletis.com in the public web crawl.
Threat posture
History
Mail and authentication
MX records
SPF policy
3 SPF mechanisms authorising senders for maletis.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf_useast2.prod.hydra.sophos.com |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | spf.protection.outlook.com |
Related pages
Pivot deeper into the graph from maletis.com.
- IP · 172.232.164.221
- ASN · AS63949AKAMAI-LINODE-AP Akamai Connected Cloud
- Registrar · iana:2
- Country · US
- Email · dh3x837b2t7@networksolutionsprivateregistration.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: "maletis.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.