go2cmo.com - dns.ninja
go2cmo.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1783261246 | ||||||
Same first word
go2cmo.com |
Similar names
com2go.ws |
com2go.com |
go2com.cn |
com2go.de |
cmo2go.ca |
com2go.biz |
com2go.net |
com2go.co.uk |
cmo2go.com |
go2com.com |
com2go.org |
cmo2go.de |
com2go.com.cy |
cmo2go.net |
com2go.co |
com2go.us |
DNS History
21 records (10 active, 11 former)
●NSns-cloud-c1.googledomains.com2026-04-09 → 2026-07-05 · 3 obs
● 2026-04-09 05:32:24
● 2026-07-05 14:21:02
●NSns-cloud-c2.googledomains.com2026-04-09 → 2026-07-05 · 3 obs
● 2026-04-09 05:32:24
● 2026-07-05 14:21:02
●NSns-cloud-c3.googledomains.com2026-04-09 → 2026-07-05 · 3 obs
● 2026-04-09 05:32:24
● 2026-07-05 14:21:02
●NSns-cloud-c4.googledomains.com2026-04-09 → 2026-07-05 · 3 obs
● 2026-04-09 05:32:24
● 2026-07-05 14:21:02
○NSns35.domaincontrol.com2017-08-10 → 2017-08-10 · 3 obs
○ 2026-04-09 05:32:24
○ 2026-07-05 14:21:02
○NSns36.domaincontrol.com2017-08-10 → 2017-08-10 · 3 obs
○ 2026-04-09 05:32:24
○ 2026-07-05 14:21:02
●MXalt1.aspmx.l.google.com2026-04-09 → 2026-07-05 · 2 obs
● 2026-07-05 14:21:02
●MXalt2.aspmx.l.google.com2026-04-09 → 2026-07-05 · 2 obs
● 2026-07-05 14:21:02
●MXalt3.aspmx.l.google.com2026-04-09 → 2026-07-05 · 2 obs
● 2026-07-05 14:21:02
●MXalt4.aspmx.l.google.com2026-04-09 → 2026-07-05 · 2 obs
● 2026-07-05 14:21:02
●MXaspmx.l.google.com2026-04-09 → 2026-07-05 · 2 obs
● 2026-07-05 14:21:02
●A172.66.0.702026-04-09 → 2026-07-05 · 3 obs
● 2026-04-09 05:32:24
● 2026-07-05 14:21:02
○A184.168.221.132017-08-10 → 2017-08-10 · 3 obs
○ 2026-04-09 05:32:24
○ 2026-07-05 14:21:02
○A184.168.221.222017-08-10 → 2017-08-10 · 3 obs
○ 2026-04-09 05:32:24
○ 2026-07-05 14:21:02
○A184.168.221.232017-08-10 → 2017-08-10 · 3 obs
○ 2026-04-09 05:32:24
○ 2026-07-05 14:21:02
○A184.168.221.262017-08-10 → 2017-08-10 · 3 obs
○ 2026-04-09 05:32:24
○ 2026-07-05 14:21:02
○A184.168.221.92017-08-10 → 2017-08-10 · 3 obs
○ 2026-04-09 05:32:24
○ 2026-07-05 14:21:02
○A50.63.202.142017-08-10 → 2017-08-10 · 3 obs
○ 2026-04-09 05:32:24
○ 2026-07-05 14:21:02
○A50.63.202.52017-08-10 → 2017-08-10 · 3 obs
○ 2026-04-09 05:32:24
○ 2026-07-05 14:21:02
○A50.63.202.72017-08-10 → 2017-08-10 · 3 obs
○ 2026-04-09 05:32:24
○ 2026-07-05 14:21:02
○A50.63.202.82017-08-10 → 2017-08-10 · 3 obs
○ 2026-04-09 05:32:24
○ 2026-07-05 14:21:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| go2cmo.com | ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.36.108
NS records: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 629ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 172.66.0.70 |
| NS | 4 | ns-cloud-c2.googledomains.com, ns-cloud-c1.googledomains.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns-cloud-c1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-c1.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com...)
Analysis
IP Addresses
go2cmo.com resolves to just one IP address, 172.66.0.70.
Two other host names, along with kobibobi.com, shydesai.com and silocon-fze.com, also share IP numbers with go2cmo.com.
Name Servers
The NS records for go2cmo.com point to four name servers: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com.
At least some of go2cmo.com's name servers are shared with other domains, for example stefanopugliese.com, bestindustrialmarketreports.com, kathleentax.com and two more.
These name servers are often deployed together with the name servers ns-127.awsdns-15.com, ns-664.awsdns-19.net, ns-1424.awsdns-50.org and ns-1660.awsdns-15.co.uk.
Four hostnames, each resolving to a pair of IP addresses: ns-cloud-c1.googledomains.com directs to 216.239.32.108 and 2001:4860:4802:32::6c; ns-cloud-c2.googledomains.com directs to 216.239.34.108 and 2001:4860:4802:34::6c; ns-cloud-c3.googledomains.com directs to 216.239.36.108 and 2001:4860:4802:36::6c; ns-cloud-c4.googledomains.com directs to 216.239.38.108 and 2001:4860:4802:38::6c.
Mail Servers
Five mail servers handle go2cmo.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between go2cmo.com and other domains, including ns500794.ns500794.ns500794.ns500821.ns500821.ns500795.ns500821.ns500821.ns500795.ns500821.ns500821.ns500795.ns500790.ns500795.lustypartnersfinder.com, ns500754.ns500731.ns500671.ns500671.ns500671.ns500688.ns500704.ns500704.ns500649.ns500291.ns500291.ns500131.lustychickser.com, dousa.eu and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
aspmx.l.google.com resolves to 142.251.167.27 and 2607:f8b0:4004:c07::1b.
alt1.aspmx.l.google.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1b.