Hostname
mbm.group
Last fetched
mbm.group resolves to 13.126.158.82, announced in 13.126.0.0/15 by AMAZON-02 - Amazon.com, Inc. in IN. mbm.group is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 13.126.158.82
13.126.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.127.63.226
13.126.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.232.38.214
13.232.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 3.108.11.240
3.108.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 3.108.118.110
3.108.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 3.111.14.73
3.108.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.206.165.231
13.204.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.206.56.38
13.204.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 13.205.207.207
IPv6 resolution
No AAAA record for mbm.group is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
- Contact emails
- mbm.group@domainsbyproxy.com
Subdomains
Showing 5 of 6. View all subdomains →
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns-203.awsdns-25.com
- ns-999.awsdns-60.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1384.awsdns-45.org
- ns-2033.awsdns-62.co.uk
MX records
- mbm-group.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
- a: mbm.group
- mx: mbm.group
- ip: 64.139.133.178
Threat-feed evidence
History
Related pages
Pivot from mbm.group into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "mbm.group"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.