metro.cloud - robtex.com
metro.cloud
cloud
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1771994133 | ||||||
PTR for
Up
www.metro.cloud |
einvoice.metro.cloud |
einvoice-pp.metro.cloud |
cf.metro.cloud |
Same first word
Similar names
DNS History
18 records (8 active, 10 former)
○NSns.metro-ag.com2016-12-29 → 2019-09-22 · 4 obs
● 2019-09-22 05:18:18
○ 2020-11-17 09:20:44
○ 2026-02-25 10:24:14
○NSns.metro.de2016-12-29 → 2019-09-22 · 4 obs
● 2019-09-22 05:18:18
○ 2020-11-17 09:20:44
○ 2026-02-25 10:24:14
○NSns.metro.info2016-12-29 → 2019-09-22 · 4 obs
● 2019-09-22 05:18:18
○ 2020-11-17 09:20:44
○ 2026-02-25 10:24:14
●NSns1.f5clouddns.com2026-02-25 → 2026-02-25 · 3 obs
● 2026-02-25 08:24:22
● 2026-02-25 10:24:14
●NSns1.f5cloudservices.com2020-11-17 → 2026-02-25 · 3 obs
● 2020-11-17 09:20:44
● 2026-02-25 10:24:14
●NSns2.f5clouddns.com2026-02-25 → 2026-02-25 · 3 obs
● 2026-02-25 08:24:22
● 2026-02-25 10:24:14
●NSns2.f5cloudservices.com2020-11-17 → 2026-02-25 · 3 obs
● 2020-11-17 09:20:44
● 2026-02-25 10:24:14
●MXmx1.hc611-36.eu.iphmx.com2026-02-25 → 2026-02-25 · 3 obs
● 2026-02-25 08:24:22
● 2026-02-25 10:24:14
●MXmx2.hc611-36.eu.iphmx.com2026-02-25 → 2026-02-25 · 3 obs
● 2026-02-25 08:24:22
● 2026-02-25 10:24:14
○MXsmtp.metro.info2016-12-29 → 2020-11-17 · 4 obs
● 2020-11-17 09:20:44
○ 2026-02-25 08:24:22
○ 2026-02-25 10:24:14
●A108.142.218.582026-02-25 → 2026-02-25 · 3 obs
● 2026-02-25 08:24:22
● 2026-02-25 10:24:14
○A164.139.14.1622016-12-29 → 2020-11-17 · 4 obs
● 2020-11-17 09:20:44
○ 2026-02-25 08:24:22
○ 2026-02-25 10:24:14
○A164.139.14.1752016-12-29 → 2019-09-22 · 4 obs
● 2019-09-22 05:18:18
○ 2020-11-17 09:20:44
○ 2026-02-25 10:24:14
○A164.61.195.992020-11-17 → 2020-11-17 · 4 obs
● 2020-11-17 09:20:44
○ 2026-02-25 08:24:22
○ 2026-02-25 10:24:14
○A164.61.205.1622016-12-29 → 2020-11-17 · 4 obs
● 2020-11-17 09:20:44
○ 2026-02-25 08:24:22
○ 2026-02-25 10:24:14
○A164.61.205.1752016-12-29 → 2019-09-22 · 4 obs
● 2019-09-22 05:18:18
○ 2020-11-17 09:20:44
○ 2026-02-25 10:24:14
○A194.156.50.992020-11-17 → 2020-11-17 · 4 obs
● 2020-11-17 09:20:44
○ 2026-02-25 08:24:22
○ 2026-02-25 10:24:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloud | ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info, ns01.trs-dns.com | - |
| metro.cloud | ns1.f5cloudservices.com, ns2.f5cloudservices.com | - |
✅ Authoritative Response
Server: 107.162.176.221
NS records: ns1.f5cloudservices.com, ns2.f5cloudservices.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for metro.cloud (unsigned zone)
⏱️ Timing
Total: 1078ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 108.142.218.58 |
| NS | 4 | ns2.f5cloudservices.com, ns1.f5clouddns.com... |
| MX | 2 | mx1.hc611-36.eu.iphmx.com (pri: 10), mx2.hc611-36.eu.iphmx.com (pri: 10) |
| TXT | 3 | MS=ms80164990, acas.mnom.io=DNSint... |
| SOA | 1 | ns.mgi.de hostmaster.metro.de |
AI analysis
metro.cloud is a parent of www.metro.cloud, einvoice.metro.cloud, einvoice-pp.metro.cloud and cf.metro.cloud.
metro.cloud points to a single IP: 108.142.218.58.
Other host names, for instance metroag.us, aro.info, metro-services.pl, metro-holding.com and metrosystems.pl share IP numbers with metro.cloud.
metro.cloud is delegated to five name servers: ns1.f5clouddns.com, ns2.f5clouddns.com, ns1.f5cloudservices.com, ns2.f5cloudservices.com and ns.mgi.de.
metro.cloud partially shares name servers with other domains; examples include johnfawknerprivatehospital.com.au, valspar.com, dhl.com.bn, accushadeeu.com and sherwin-williams.com.ve.
These name servers are commonly used alongside ns.metro-ag.com, ns.metro.de, ns.metro.info, a1-16.akam.net, a10-64.akam.net, a11-66.akam.net, a13-65.akam.net, a2-67.akam.net, a28-65.akam.net and ns5.dnsmadeeasy.com.
Two IP numbers per host:
ns1.f5clouddns.com points to 2604:e180:1071::3:1 and 107.162.234.197
ns2.f5clouddns.com points to 2604:e180:1071::ffff:6ba2:b0dd and 107.162.176.221
ns1.f5cloudservices.com points to 2604:e180:1071::3:1 and 107.162.234.197
ns2.f5cloudservices.com points to 2604:e180:1071::ffff:6ba2:b0dd and 107.162.176.221
One IP number:
ns.mgi.de points to 164.61.210.140
Hosts that point to 2604:e180:1071::3:1: ns1.f5clouddns.com and ns1.f5cloudservices.com
Hosts that point to 107.162.234.197: ns1.f5clouddns.com and ns1.f5cloudservices.com
Hosts that point to 2604:e180:1071::ffff:6ba2:b0dd: ns2.f5clouddns.com and ns2.f5cloudservices.com
Hosts that point to 107.162.176.221: ns2.f5clouddns.com and ns2.f5cloudservices.com
metro.cloud is handled by two mail servers: mx1.hc611-36.eu.iphmx.com and mx2.hc611-36.eu.iphmx.com.
metro.cloud has the same mail server setup as other domains, including makro.be, rungis-group.com, metro-ag.com, mgh.metro-ag.de and aspiag.ch.
metro.cloud shares some mail servers with other domains, at least partially, such as metro-mgl.ru, myfasol.ru, metro-expo.ru, metro-partner.ru and megustro.com.
Host names with two IPs
mx1.hc611-36.eu.iphmx.com points to: 23.90.104.169 and 207.54.77.186.
mx2.hc611-36.eu.iphmx.com points to: 23.90.104.169 and 207.54.77.186.
Host names that point to 23.90.104.169: mx1.hc611-36.eu.iphmx.com and mx2.hc611-36.eu.iphmx.com.
Host names that point to 207.54.77.186: mx1.hc611-36.eu.iphmx.com and mx2.hc611-36.eu.iphmx.com.