Hostname
emamigroup.com
Last fetched
emamigroup.com resolves to 43.204.190.105, announced in 43.204.0.0/15 by AMAZON-02 - Amazon.com, Inc. in IN. emamigroup.com 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
- 43.204.190.105
43.204.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
IPv6 resolution
No AAAA record for emamigroup.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- bipin jaiswal
- Contact emails
- bipin.jaiswal@emamigroup.com
Subdomains
| Subdomain |
|---|
| autodiscover.emamigroup.com |
| emamihelpdesk.emamigroup.com |
| emamivc.emamigroup.com |
| lyncdiscover.emamigroup.com |
| spf1.emamigroup.com |
| tmedgerelay.emamigroup.com |
| www.emamigroup.com |
Showing 7 of 7 subdomains (7 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns-468.awsdns-58.com
- ns-965.awsdns-56.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-1235.awsdns-26.org
- ns-1605.awsdns-08.co.uk
MX records
- emamigroup.in.tmes-in.trendmicro.com
SPF policy
- ip: 199.255.27.110/32
- ip: 20.204.32.117/32
- ip: 13.126.102.198/32
- ip: 4.213.39.212/32
- ip: 13.126.94.72/32
- ip: 150.129.176.86/32
- mx: emamigroup.com
- include: spf1.emamigroup.com
- include: spf.protection.outlook.com
- include: spf.tmes-in.trendmicro.com
Threat-feed evidence
History
Related pages
Pivot from emamigroup.com 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: "emamigroup.com"})-[: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.