Hostname
memd.me
Last fetched
memd.me resolves to 12 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
memd.me resolves to 12 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 100.28.182.188 | 100.24.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 16.146.239.123 | 16.146.128.0/17 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 35.164.5.97 | 35.160.0.0/13 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 44.224.76.221 | 44.224.0.0/11 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.10.25.123 | 52.10.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.6.119.18 | 52.4.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.89.35.201 | 52.88.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 54.70.169.50 | 54.70.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 54.85.110.6 | 54.84.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.88.168.251 | 54.88.0.0/16 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 184.32.101.111 | 184.32.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | — |
| 44.232.59.141 | 44.224.0.0/11 | AS16509 | AMAZON-02 - Amazon.com, Inc. | — |
WHOIS identity
- Registrar
- iana:146
- Organization
- amy white
- Contact emails
Subdomains
38 observed subdomains of memd.me.
Showing 25 of 38. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from memd.me in the public web crawl.
105 sites link to this hostname.
28 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
6 SPF mechanisms authorising senders for memd.me.
| Mechanism | Target |
|---|---|
| SPF_A | memd.me |
| SPF_INCLUDE | _netblocks.walmart.com |
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | _spf.salesforce.com |
| SPF_INCLUDE | servers.mcsv.net |
| SPF_MX | memd.me |
Related pages
Pivot deeper into the graph from memd.me.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "memd.me"})-[: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.