solosegment.com - dns.ninja

`solosegment.com`

DNSSEC	⚠️ Not signed
NS	`ns-707.awsdns-24.net` ⭐
		A	2600:9000:5302:c300::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-707.awsdns-24.net`
		A	205.251.194.195^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-707.awsdns-24.net`
NS	`ns-11.awsdns-01.com`
		A	2600:9000:5300:b00::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-11.awsdns-01.com`
		A	205.251.192.11^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-11.awsdns-01.com`
NS	`ns-1434.awsdns-51.org`
		A	2600:9000:5305:9a00::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1434.awsdns-51.org`
		A	205.251.197.154^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1434.awsdns-51.org`
NS	`ns-1597.awsdns-07.co.uk`
		A	2600:9000:5306:3d00::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1597.awsdns-07.co.uk`
		A	205.251.198.61^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1597.awsdns-07.co.uk`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	64.233.180.27^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
MX	`ndwinwk7r4nnuevxhmwkcb6seoomaivsk343xircackkw4x7in5a.mx-verification.google.com`⁽¹⁵⁾
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns-707.awsdns-24.net`awsdns-hostmaster@amazon.com serial=1

`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.net`nstld@verisign-grs.com serial=1786764129

⚠️ On DNS blocklist: pro, pro.mini, pro.plus, pro.plus.mini, ultimate, ultimate.mini
WOT: UNKNOWN (34/100)

Same first word

solosegment.com

DNS History

22 records (10 active, 12 former)

○NSns-1001.awsdns-61.net2016-12-21 → 2016-12-21 · 3 obs

● 2016-12-21 01:05:28
○ 2017-11-14 13:17:08
○ 2026-08-15 03:42:32

○NSns-1081.awsdns-07.org2016-12-21 → 2016-12-21 · 3 obs

● 2016-12-21 01:05:28
○ 2017-11-14 13:17:08
○ 2026-08-15 03:42:32

●NSns-11.awsdns-01.com2026-02-16 → 2026-08-15 · 3 obs

○ 2017-11-14 13:17:08
● 2026-02-16 07:19:38
● 2026-08-15 03:42:32

○NSns-1240.awsdns-27.org2017-11-14 → 2017-11-14 · 4 obs

○ 2016-12-21 01:05:28
● 2017-11-14 13:17:08
○ 2026-02-16 07:19:38
○ 2026-08-15 03:42:32

●NSns-1434.awsdns-51.org2026-02-16 → 2026-08-15 · 3 obs

○ 2017-11-14 13:17:08
● 2026-02-16 07:19:38
● 2026-08-15 03:42:32

●NSns-1597.awsdns-07.co.uk2026-02-16 → 2026-08-15 · 3 obs

○ 2017-11-14 13:17:08
● 2026-02-16 07:19:38
● 2026-08-15 03:42:32

○NSns-1630.awsdns-11.co.uk2017-11-14 → 2017-11-14 · 4 obs

○ 2016-12-21 01:05:28
● 2017-11-14 13:17:08
○ 2026-02-16 07:19:38
○ 2026-08-15 03:42:32

○NSns-1690.awsdns-19.co.uk2016-12-21 → 2016-12-21 · 3 obs

● 2016-12-21 01:05:28
○ 2017-11-14 13:17:08
○ 2026-08-15 03:42:32

○NSns-310.awsdns-38.com2016-12-21 → 2016-12-21 · 3 obs

● 2016-12-21 01:05:28
○ 2017-11-14 13:17:08
○ 2026-08-15 03:42:32

○NSns-330.awsdns-41.com2017-11-14 → 2017-11-14 · 4 obs

○ 2016-12-21 01:05:28
● 2017-11-14 13:17:08
○ 2026-02-16 07:19:38
○ 2026-08-15 03:42:32

○NSns-647.awsdns-16.net2017-11-14 → 2017-11-14 · 4 obs

○ 2016-12-21 01:05:28
● 2017-11-14 13:17:08
○ 2026-02-16 07:19:38
○ 2026-08-15 03:42:32

●NSns-707.awsdns-24.net2026-02-16 → 2026-08-15 · 3 obs

○ 2017-11-14 13:17:08
● 2026-02-16 07:19:38
● 2026-08-15 03:42:32

●MXalt1.aspmx.l.google.com2016-12-21 → 2026-08-15 · 2 obs

● 2016-12-21 01:05:28
● 2026-08-15 03:42:32

●MXalt2.aspmx.l.google.com2016-12-21 → 2026-08-15 · 2 obs

● 2016-12-21 01:05:28
● 2026-08-15 03:42:32

●MXalt3.aspmx.l.google.com2026-02-16 → 2026-08-15 · 3 obs

○ 2017-11-14 13:17:08
● 2026-02-16 07:19:38
● 2026-08-15 03:42:32

●MXalt4.aspmx.l.google.com2026-02-16 → 2026-08-15 · 3 obs

○ 2017-11-14 13:17:08
● 2026-02-16 07:19:38
● 2026-08-15 03:42:32

●MXaspmx.l.google.com2016-12-21 → 2026-08-15 · 2 obs

● 2016-12-21 01:05:28
● 2026-08-15 03:42:32

○MXaspmx2.googlemail.com2016-12-21 → 2017-11-14 · 4 obs

● 2016-12-21 01:05:28
● 2017-11-14 13:17:08
○ 2026-02-16 07:19:38
○ 2026-08-15 03:42:32

○MXaspmx3.googlemail.com2016-12-21 → 2017-11-14 · 4 obs

● 2016-12-21 01:05:28
● 2017-11-14 13:17:08
○ 2026-02-16 07:19:38
○ 2026-08-15 03:42:32

●MXndwinwk7r4nnuevxhmwkcb6seoomaivsk343xircackkw4x7in5a.mx-verification.google.com2026-02-16 → 2026-08-15 · 3 obs

○ 2017-11-14 13:17:08
● 2026-02-16 07:19:38
● 2026-08-15 03:42:32

○A37.60.253.1142016-12-21 → 2016-12-21 · 3 obs

● 2016-12-21 01:05:28
○ 2017-11-14 13:17:08
○ 2026-08-15 03:42:32

○A77.104.136.2072017-11-14 → 2026-02-17 · 5 obs

○ 2016-12-21 01:05:28
● 2017-11-14 13:17:08
● 2026-02-17 00:27:32
○ 2026-02-19 02:55:38
○ 2026-08-15 03:42:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, a.gtld-servers.net...	-
solosegment.com	ns-11.awsdns-01.com, ns-707.awsdns-24.net, ns-1597.awsdns-07.co.uk, ns-1434.awsdns-51.org	2 records

✅ Authoritative Response

Server:205.251.192.11

NS records: ns-11.awsdns-01.com, ns-707.awsdns-24.net, ns-1597.awsdns-07.co.uk, ns-1434.awsdns-51.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for solosegment.com (unsigned zone)

⏱️ Timing

Total: 761ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-11.awsdns-01.com, ns-1434.awsdns-51.org...`
MX	6	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	1	`v=spf1 include:_spf.google.com ~all`
SOA	1	`ns-707.awsdns-24.net awsdns-hostmaster.a`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-11.awsdns-01.com, ns-11.awsdns-01.com)

Analysis

Name Servers

The authoritative name servers for solosegment.com are ns-11.awsdns-01.com, ns-707.awsdns-24.net, ns-1434.awsdns-51.org and ns-1597.awsdns-07.co.uk.

solosegment.com has at least partial name server overlap with other domains, such as gsqr.com, techwiser.net, maggicaminhoes.com.br and two others.

These name servers tend to appear together with the name servers ns-305.awsdns-38.com, ns-900.awsdns-48.net and ns-1576.awsdns-05.co.uk.

ns-11.awsdns-01.com, ns-707.awsdns-24.net, ns-1434.awsdns-51.org and ns-1597.awsdns-07.co.uk all point to exactly two IP numbers each: ns-11.awsdns-01.com → 205.251.192.11 and 2600:9000:5300:b00::1; ns-707.awsdns-24.net → 205.251.194.195 and 2600:9000:5302:c300::1; ns-1434.awsdns-51.org → 205.251.197.154 and 2600:9000:5305:9a00::1; ns-1597.awsdns-07.co.uk → 205.251.198.61 and 2600:9000:5306:3d00::1.

Mail Servers

Mail for solosegment.com is routed through 6 mail servers, including aspmx.l.google.com, ndwinwk7r4nnuevxhmwkcb6seoomaivsk343xircackkw4x7in5a.mx-verification.google.com, alt1.aspmx.l.google.com and 3 other.

solosegment.com has at least partial mail server overlap with other domains such as ns500671.ns500671.ns500671.ns500754.ns500649.ns500678.ns500678.ns500671.ns500666.ns500291.ns500131.lustychickser.com, ns500731.ns500754.ns500731.ns500671.ns500731.ns500705.ns500704.ns500704.ns500704.ns500671.ns500649.ns500666.ns500653.ns500153.tenderladiesbz.com, sakuraken.com and two more.

These mail servers commonly appear together with alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and two other mail servers.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com resolves to two addresses: 64.233.180.27 and 2607:f8b0:4004:c1b::1a.

alt1.aspmx.l.google.com resolves to two addresses: 192.178.234.26 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.27 and 2a00:1450:400c:c23::1a.