Hostname
e.m.me
Last fetched
e.m.me resolves to 2 IPv4 addresses operated by FACEBOOK - Facebook, Inc. in DK.
Nutrition Label
Resolution chain
e.m.me 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 |
|---|---|---|---|---|
| 157.240.200.16 | 157.240.200.0/24 | AS32934 | FACEBOOK - Facebook, Inc. | DK |
| 208.91.112.55 | 208.91.112.0/24 | AS40934 | FORTINET - Fortinet Inc. | US |
| 208.91.112.55 | 208.91.112.0/24 | AS40934 | FORTINET - Fortinet Inc. | CA |
WHOIS identity
No WHOIS records are currently associated with e.m.me in WhisperGraph.
Subdomains
1 observed subdomain of e.m.me.
| Subdomain |
|---|
| r.e.m.me |
Threat posture
History
Mail and authentication
MX records
SPF policy
1 SPF mechanism authorising senders for e.m.me.
| Mechanism | Target |
|---|---|
| SPF_A | e.m.me |
Related pages
Pivot deeper into the graph from e.m.me.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "e.m.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.