problem-solving.net - dns.ninja

`problem-solving.net`

DNSSEC	⚠️ Not signed
A	2a00:6d40:4:3::c228:81^{🇮🇹 ARUBA-ASN2a00:6d40::/32 Aruba S.p.A. IPv6 Network}
A	89.46.105.81^{🇮🇹 ARUBA-ASN89.46.104.0/21 Aruba S.p.A. Network}
NS	`dns2.technorail.com` ⭐
		A	2a00:6d42:3:2096::f:1^{🇮🇹 ARUBA-ASN2a00:6d42::/32 Aruba S.p.A. IPv6 Network}
			PTR	`dns2.technorail.com`
		A	95.110.136.8^{🇮🇹 ARUBA-ASN95.110.136.0/21 Aruba S.p.A. Network}
			PTR	`dns2.technorail.com`
NS	`dns.technorail.com`
		A	2a00:6d40:2:2082::f:1^{🇮🇹 ARUBA-ASN2a00:6d40::/32 Aruba S.p.A. IPv6 Network}
			PTR	`dns.technorail.com`
		A	94.177.210.13^{🇮🇹 ARUBA-ASN94.177.208.0/22 Aruba S.p.A. Network}
			PTR	`dns.technorail.com`
NS	`dns3.arubadns.net`
		A	2a00:6d41:3:206e::f:1^{🇮🇹 ARUBA-ASN2a00:6d41::/32 Aruba S.p.A. IPv6 Network}
			PTR	`dns3.arubadns.net`
		A	95.110.220.5^{🇮🇹 ARUBA-ASN95.110.192.0/18 Aruba S.p.A. Network}
			PTR	`dns3.arubadns.net`
NS	`dns4.arubadns.cz`
		A	2001:15e8:104:4::d8ee^{🇨🇿 INTERNET-CZ2001:15e8::/32}
			PTR	`dns4.arubadns.cz`
		A	81.2.216.238^{🇨🇿 INTERNET-CZ81.2.192.0/18 INTERNET CZ, a.s.}
			PTR	`dns4.arubadns.cz`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c17::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f27.1e100.net`
		A	142.251.163.27^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽²⁰⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.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.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`aspmx2.googlemail.com`⁽⁵⁰⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
TXT	`google-site-verification=w9OOvxzNFy-BK1w_IakALPJ6qUDSA2PIFjchN2lgFIY`
TXT	`google-site-verification=iwO1Edbr1XiHI5y5gFJohT2r7z7pmEy_BZcbrvHNdsQ`
SOA	`dns.technorail.com`hostmaster@problem-solving.net 2026-04-08 #2

`net`

	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=1782119610

Same first word

problem-solving.de

problem-solving.ch

problem-solving.info

problem-solving.cz

problem-solving.ru

problem-solving.net

problem-solving.com

problem-solving.org

problem-solving.fr

DNS History

22 records (10 active, 12 former)

●NSdns.technorail.com2015-05-23 → 2026-06-22 · 2 obs

● 2015-05-23 18:36:34
● 2026-06-22 09:26:02

●NSdns2.technorail.com2015-05-23 → 2026-06-22 · 2 obs

● 2015-05-23 18:36:34
● 2026-06-22 09:26:02

●NSdns3.arubadns.net2015-05-23 → 2026-06-22 · 2 obs

● 2015-05-23 18:36:34
● 2026-06-22 09:26:02

●NSdns4.arubadns.cz2015-05-23 → 2026-06-22 · 2 obs

● 2015-05-23 18:36:34
● 2026-06-22 09:26:02

●MXalt1.aspmx.l.google.com2017-03-27 → 2026-06-22 · 3 obs

○ 2016-07-24 14:02:48
● 2017-03-27 14:40:22
● 2026-06-22 09:26:02

●MXalt2.aspmx.l.google.com2017-03-27 → 2026-06-22 · 3 obs

○ 2016-07-24 14:02:48
● 2017-03-27 14:40:22
● 2026-06-22 09:26:02

●MXaspmx.l.google.com2017-03-27 → 2026-06-22 · 3 obs

○ 2016-07-24 14:02:48
● 2017-03-27 14:40:22
● 2026-06-22 09:26:02

●MXaspmx2.googlemail.com2017-03-27 → 2026-06-22 · 3 obs

○ 2016-07-24 14:02:48
● 2017-03-27 14:40:22
● 2026-06-22 09:26:02

○MXmx.problem-solving.net2015-05-23 → 2016-07-24 · 4 obs

● 2015-05-23 18:36:34
● 2016-07-24 14:02:48
○ 2017-03-27 14:40:22
○ 2026-06-22 09:26:02

○A178.33.183.1472015-10-16 → 2015-12-31 · 5 obs

○ 2015-05-23 18:36:34
● 2015-10-16 17:33:16
● 2015-12-31 11:37:24
○ 2016-03-27 08:49:54
○ 2026-06-22 09:26:02

●A2a00:6d40:4:3::c228:812026-02-28 → 2026-06-22 · 3 obs

○ 2020-09-07 18:22:02
● 2026-02-28 23:41:22
● 2026-06-22 09:26:02

○A37.59.238.922016-03-27 → 2016-07-24 · 5 obs

○ 2015-12-31 11:37:24
● 2016-03-27 08:49:54
● 2016-07-24 14:02:48
○ 2017-03-27 14:40:22
○ 2026-06-22 09:26:02

○A5.135.255.2482015-05-23 → 2015-05-23 · 3 obs

● 2015-05-23 18:36:34
○ 2015-10-16 17:33:16
○ 2026-06-22 09:26:02

○A62.149.128.1512017-03-27 → 2020-09-07 · 5 obs

○ 2016-07-24 14:02:48
● 2017-03-27 14:40:22
● 2020-09-07 18:22:02
○ 2026-02-28 23:41:22
○ 2026-06-22 09:26:02

○A62.149.128.1542017-03-27 → 2020-09-07 · 5 obs

○ 2016-07-24 14:02:48
● 2017-03-27 14:40:22
● 2020-09-07 18:22:02
○ 2026-02-28 23:41:22
○ 2026-06-22 09:26:02

○A62.149.128.1572017-03-27 → 2020-09-07 · 5 obs

○ 2016-07-24 14:02:48
● 2017-03-27 14:40:22
● 2020-09-07 18:22:02
○ 2026-02-28 23:41:22
○ 2026-06-22 09:26:02

○A62.149.128.1602017-03-27 → 2020-09-07 · 5 obs

○ 2016-07-24 14:02:48
● 2017-03-27 14:40:22
● 2020-09-07 18:22:02
○ 2026-02-28 23:41:22
○ 2026-06-22 09:26:02

○A62.149.128.1632017-03-27 → 2020-09-07 · 5 obs

○ 2016-07-24 14:02:48
● 2017-03-27 14:40:22
● 2020-09-07 18:22:02
○ 2026-02-28 23:41:22
○ 2026-06-22 09:26:02

○A62.149.128.1662017-03-27 → 2020-09-07 · 5 obs

○ 2016-07-24 14:02:48
● 2017-03-27 14:40:22
● 2020-09-07 18:22:02
○ 2026-02-28 23:41:22
○ 2026-06-22 09:26:02

○A62.149.128.722017-03-27 → 2020-09-07 · 5 obs

○ 2016-07-24 14:02:48
● 2017-03-27 14:40:22
● 2020-09-07 18:22:02
○ 2026-02-28 23:41:22
○ 2026-06-22 09:26:02

○A62.149.128.742017-03-27 → 2020-09-07 · 5 obs

○ 2016-07-24 14:02:48
● 2017-03-27 14:40:22
● 2020-09-07 18:22:02
○ 2026-02-28 23:41:22
○ 2026-06-22 09:26:02

●A89.46.105.812026-02-28 → 2026-06-22 · 3 obs

○ 2020-09-07 18:22:02
● 2026-02-28 23:41:22
● 2026-06-22 09:26:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	g.gtld-servers.net, a.gtld-servers.net, i.gtld-servers.net, c.gtld-servers.net...	-
problem-solving.net	dns2.technorail.com, dns.technorail.com, dns4.arubadns.cz, dns3.arubadns.net	2 records

✅ Authoritative Response

Server:94.177.210.13

NS records: dns2.technorail.com, dns.technorail.com, dns4.arubadns.cz, dns3.arubadns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for problem-solving.net (unsigned zone)

⏱️ Timing

Total: 2098ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`89.46.105.81`
AAAA	1	`2a00:6d40:4:3::c228:81`
NS	4	`dns4.arubadns.cz, dns2.technorail.com...`
MX	4	`alt1.aspmx.l.google.com (pri: 20), aspmx.l.google.com (pri: 10)...`
TXT	2	`google-site-verification=iwO1Edbr1XiHI5y, google-site-verification=w9OOvxzNFy-BK1w`
SOA	1	`dns.technorail.com hostmaster.problem-so`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns3.arubadns.net, dns3.arubadns.net)

Analysis

IP Addresses

problem-solving.net resolves to the IP addresses 89.46.105.81 and 2a00:6d40:4:3::c228:81

studiolegaleinnocenti.com, lautoanoleggio.it, enjoycatania.com and two other host names share IP numbers with problem-solving.net.

Name Servers

The authoritative name servers for problem-solving.net are dns2.technorail.com, dns.technorail.com, dns4.arubadns.cz and dns3.arubadns.net.

problem-solving.net has at least partial name server overlap with other domains, such as postaservice.it, sellepanebianco.it, angolodimara.it and two others.

dns2.technorail.com, dns.technorail.com, dns4.arubadns.cz and dns3.arubadns.net all point to exactly two IP numbers each: dns2.technorail.com → 95.110.136.8 and 2a00:6d42:3:2096::f:1; dns.technorail.com → 94.177.210.13 and 2a00:6d40:2:2082::f:1; dns4.arubadns.cz → 81.2.216.238 and 2001:15e8:104:4::d8ee; dns3.arubadns.net → 95.110.220.5 and 2a00:6d41:3:206e::f:1.

Mail Servers

problem-solving.net has four mail servers: aspmx2.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.

problem-solving.net has at least partial mail server overlap with other domains such as ellsworthbikes.com, sharpestu.com, ns500693.ns500734.ns500693.ns500693.ns500734.ns500734.ns500699.ns500734.ns500699.ns500588.ns500588.ns500588.ns500632.ns500632.ns500588.ns500588.ns500588.dtrkdll.com and two more.

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

Four hostnames each resolve to two IP addresses: aspmx2.googlemail.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1b; aspmx.l.google.com resolves to 142.251.163.27 and 2607:f8b0:4004:c17::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::1a.

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.27 IP addresses each.