Hostname
m4marry.com
Last fetched
m4marry.com resolves to 6 IPv4 addresses operated by AKAMAI-AS - Akamai Technologies, Inc. in DE. WHOIS lists iana:2 as the registrar.
Nutrition Label
Resolution chain
m4marry.com resolves to 6 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 2.23.244.46 | 2.23.244.0/22 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | DE |
| 23.37.16.44 | 23.37.16.0/22 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | US |
| 23.52.180.37 | 23.52.180.0/22 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | DE |
| 23.56.162.48 | 23.56.162.0/23 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | US |
| 23.58.108.42 | 23.32.0.0/11 | AS20940 | — | DE |
| 88.221.168.212 | 88.221.168.0/22 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | DE |
WHOIS identity
- Registrar
- iana:2
- Organization
- malayala manorama
- Contact emails
Subdomains
19 observed subdomains of m4marry.com.
Web-graph footprint
Distinct hostnames that link to or from m4marry.com in the public web crawl.
34 sites link to this hostname.
21 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
8 SPF mechanisms authorising senders for m4marry.com.
| Mechanism | Target |
|---|---|
| SPF_A | m4marry.com |
| SPF_IP | 121.243.126.46 |
| SPF_IP | 122.15.253.133 |
| SPF_IP | 125.17.109.42 |
| SPF_IP | 14.140.179.94 |
| SPF_IP | 210.212.238.194 |
| SPF_IP | 220.227.88.34 |
| SPF_MX | mail.mm.co.in |
Related pages
Pivot deeper into the graph from m4marry.com.
- IP · 2.23.244.46
- ASN · AS16625AKAMAI-AS - Akamai Technologies, Inc.
- Registrar · iana:2
- Country · DE
- Email · vvjacob@hotmail.com
- TLD · .com
- Browse hostnames · m4…
- 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: "m4marry.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.