Hostname
2mrt.top
Last fetched
2mrt.top resolves to 199.59.243.228, announced in 199.59.243.0/24 by AMAZON-02 - Amazon.com, Inc. in US. 2mrt.top 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
- 199.59.243.228
- 20.210.105.241
20.192.0.0/10 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation
- 20.44.191.172
20.40.0.0/13 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation
- 48.218.158.184
48.216.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation
- 20.89.36.238
20.64.0.0/10 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Saitama, JP
- 4.190.10.13
4.176.0.0/12 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation
- 4.214.208.185
4.208.0.0/12 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation
IPv6 resolution
No AAAA record for 2mrt.top is recorded in WhisperGraph.
Attribution
Azure
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:3804
- Registrant organisation
- privacyguardian.org
Subdomains
Showing 3 of 3 subdomains (3 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.
Mail and authentication
Nameservers
- a.zdnscloud.cn
- b.zdnscloud.cn
- f.zdnscloud.cn
- i.zdnscloud.cn
- ns1.bodis.com
- ns2.bodis.com
- ult01.dnspod.com
- ult02.dnspod.com
- ns3.mismes.com
- ns4.mismes.com
- c.zdnscloud.com
- d.zdnscloud.com
- j.zdnscloud.com
- 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
- e.zdnscloud.cn
Threat-feed evidence
History
Related pages
Pivot from 2mrt.top 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: "2mrt.top"})-[: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.