nextsegment.com - dns.ninja
nextsegment.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=1784561657 | ||||||
Previously MX for
nextsegment.com |
Same first word
nextsegment.com |
Similar names
DNS History
20 records (7 active, 13 former)
●NSdns1.registrar-servers.com2026-04-06 → 2026-07-20 · 3 obs
● 2026-04-06 09:43:42
● 2026-07-20 15:48:40
●NSdns2.registrar-servers.com2026-04-06 → 2026-07-20 · 3 obs
● 2026-04-06 09:43:42
● 2026-07-20 15:48:40
○NSns1.renewyourname.net2016-04-15 → 2016-04-15 · 4 obs
● 2016-04-15 06:56:30
○ 2016-11-26 21:31:50
○ 2026-07-20 15:48:40
○NSns1.sedoparking.com2016-11-26 → 2017-12-01 · 5 obs
● 2016-11-26 21:31:50
● 2017-12-01 20:19:58
○ 2026-04-06 09:43:42
○ 2026-07-20 15:48:40
○NSns1765.hostgator.com2015-06-07 → 2016-01-20 · 4 obs
● 2016-01-20 11:19:40
○ 2016-04-15 06:56:30
○ 2026-07-20 15:48:40
○NSns1766.hostgator.com2015-06-07 → 2016-01-20 · 4 obs
● 2016-01-20 11:19:40
○ 2016-04-15 06:56:30
○ 2026-07-20 15:48:40
○NSns2.renewyourname.net2016-04-15 → 2016-04-15 · 4 obs
● 2016-04-15 06:56:30
○ 2016-11-26 21:31:50
○ 2026-07-20 15:48:40
○NSns2.sedoparking.com2016-11-26 → 2017-12-01 · 5 obs
● 2016-11-26 21:31:50
● 2017-12-01 20:19:58
○ 2026-04-06 09:43:42
○ 2026-07-20 15:48:40
○NSns8257.hostgator.com2015-06-07 → 2016-01-20 · 4 obs
● 2016-01-20 11:19:40
○ 2016-04-15 06:56:30
○ 2026-07-20 15:48:40
●MXalt1.aspmx.l.google.com2026-04-06 → 2026-07-20 · 3 obs
● 2026-04-06 09:43:42
● 2026-07-20 15:48:40
●MXalt2.aspmx.l.google.com2026-04-06 → 2026-07-20 · 3 obs
● 2026-04-06 09:43:42
● 2026-07-20 15:48:40
●MXaspmx.l.google.com2026-04-06 → 2026-07-20 · 3 obs
● 2026-04-06 09:43:42
● 2026-07-20 15:48:40
●MXaspmx2.googlemail.com2026-04-06 → 2026-07-20 · 3 obs
● 2026-04-06 09:43:42
● 2026-07-20 15:48:40
●MXaspmx3.googlemail.com2026-04-06 → 2026-07-20 · 3 obs
● 2026-04-06 09:43:42
● 2026-07-20 15:48:40
○MXlocalhost2016-11-26 → 2017-12-01 · 5 obs
● 2016-11-26 21:31:50
● 2017-12-01 20:19:58
○ 2026-04-06 09:43:42
○ 2026-07-20 15:48:40
○MXnextsegment.com2015-06-07 → 2016-01-20 · 4 obs
● 2016-01-20 11:19:40
○ 2016-04-15 06:56:30
○ 2026-07-20 15:48:40
○A192.185.48.1852015-06-07 → 2016-01-20 · 4 obs
● 2016-01-20 11:19:40
○ 2016-04-15 06:56:30
○ 2026-07-20 15:48:40
○A69.172.201.2172016-04-15 → 2016-04-15 · 4 obs
● 2016-04-15 06:56:30
○ 2016-11-26 21:31:50
○ 2026-07-20 15:48:40
○A72.52.4.1222017-12-01 → 2017-12-01 · 4 obs
● 2017-12-01 20:19:58
○ 2026-04-06 09:43:42
○ 2026-07-20 15:48:40
○A72.52.4.912016-11-26 → 2016-11-26 · 4 obs
● 2016-11-26 21:31:50
○ 2017-12-01 20:19:58
○ 2026-07-20 15:48:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, m.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net... | - |
| nextsegment.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.132.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for nextsegment.com (unsigned zone)
⏱️ Timing
Total: 1150ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | google-site-verification=nMuhNiypzqphUo0 |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
Name Servers
nextsegment.com is served by two delegated name servers, dns1.registrar-servers.com and dns2.registrar-servers.com.
nextsegment.com shares its NS records with other domains, for example paoqu.com, socketpro.support, gredonnawilkerson.online and two others.
The name servers of nextsegment.com overlap at least partially with those of other domains — among them startwomen.org, cozycornerbooksandgifts.com, carnames.net and two more.
The name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com are commonly seen alongside these name servers.
Each of the two host names carries two IP addresses: dns1.registrar-servers.com points to 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com points to 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
Five mail servers handle nextsegment.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between nextsegment.com and other domains, including thekillingerteam.com, inboda.io, dh115119.bennington.edu and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com maps to two IP addresses — 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com maps to two IP addresses — 172.253.122.27 and 2607:f8b0:4004:c06::1b.
alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1b.
These two host names — aspmx2.googlemail.com and alt1.aspmx.l.google.com — each point to 2800:3f0:4003:c0f::1b IP addresses.
These two host names — aspmx2.googlemail.com and alt1.aspmx.l.google.com — each point to 108.177.123.27 IP addresses.