ip-addr.es - dns.ninja

`ip-addr.es`

DNSSEC	⚠️ Not signed
A	188.165.164.184^{🇫🇷 OVH188.165.0.0/16 ISP Paris, France}
		PTR	`dynamicplus.it`
NS	`ns.ip-addr.es` ⭐
		A	91.121.216.105^{🇫🇷 OVH91.121.0.0/16 ISP Paris, France}
			PTR	`dynamicplus.it`
NS	`dns.ip-addr.es`
		A	213.251.188.141^{🇫🇷 OVH213.251.128.0/18 ISP Paris, France}
			PTR	`sdns2.ovh.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c17::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f26.1e100.net`
		A	172.253.63.26^{🇺🇸 Google172.253.63.0/24}
			PTR	`bi-in-f26.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:c01::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`di-in-f27.1e100.net`
		A	74.125.193.27^{🇺🇸 Google74.125.193.0/24}
			PTR	`di-in-f27.1e100.net`
			PTR	`ig-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.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.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`v=spf1 redirect=_spf.dynamicplus.it`
SOA	`ns.ip-addr.es`hostmaster@ip-addr.es 2020-10-07 #2

`es`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns1.nic.es` ⭐
	NS	`a.nic.es`
	NS	`c.nic.es`
	NS	`g.nic.es`
	NS	`h.nic.es`
	SOA	`ns1.nic.es`hostmaster@nic.es 2026-07-31 #3

⚠️ On DNS blocklist: tif
🔒 HSTS Preload (+subdomains)

Subdomains

ns.ip-addr.es

dns.ip-addr.es

www.ip-addr.es

Same first word

ip-addr.ru

ip-addr.es

ip-addr.uk

ip-addr.info

ip-addr.net

ip-addr.de

ip-addr.com

Similar names

dri-pad.com

DNS History

21 records (8 active, 13 former)

●NSdns.ip-addr.es2026-02-19 → 2026-07-31 · 3 obs

○ 2017-09-11 16:03:30
● 2026-02-19 19:57:08
● 2026-07-31 11:49:18

●NSns.ip-addr.es2026-02-19 → 2026-07-31 · 3 obs

○ 2017-09-11 16:03:30
● 2026-02-19 19:57:08
● 2026-07-31 11:49:18

○NSns1.ip-addr.es2015-09-03 → 2017-09-11 · 4 obs

● 2015-09-03 19:30:16
● 2017-09-11 16:03:30
○ 2026-02-19 19:57:08
○ 2026-07-31 11:49:18

○NSns2.ip-addr.es2015-09-03 → 2017-09-11 · 4 obs

● 2015-09-03 19:30:16
● 2017-09-11 16:03:30
○ 2026-02-19 19:57:08
○ 2026-07-31 11:49:18

○NSns3.ip-addr.es2015-09-03 → 2017-09-11 · 4 obs

● 2015-09-03 19:30:16
● 2017-09-11 16:03:30
○ 2026-02-19 19:57:08
○ 2026-07-31 11:49:18

○NSns4.ip-addr.es2015-09-03 → 2017-09-11 · 4 obs

● 2015-09-03 19:30:16
● 2017-09-11 16:03:30
○ 2026-02-19 19:57:08
○ 2026-07-31 11:49:18

○NSnsx.ip-addr.es2015-09-03 → 2017-09-11 · 4 obs

● 2015-09-03 19:30:16
● 2017-09-11 16:03:30
○ 2026-02-19 19:57:08
○ 2026-07-31 11:49:18

●MXalt1.aspmx.l.google.com2015-09-03 → 2026-07-31 · 2 obs

● 2015-09-03 19:30:16
● 2026-07-31 11:49:18

●MXalt2.aspmx.l.google.com2015-09-03 → 2026-07-31 · 2 obs

● 2015-09-03 19:30:16
● 2026-07-31 11:49:18

●MXalt3.aspmx.l.google.com2016-12-23 → 2026-07-31 · 3 obs

○ 2016-12-06 19:43:02
● 2016-12-23 20:26:20
● 2026-07-31 11:49:18

●MXalt4.aspmx.l.google.com2016-12-23 → 2026-07-31 · 3 obs

○ 2016-12-06 19:43:02
● 2016-12-23 20:26:20
● 2026-07-31 11:49:18

●MXaspmx.l.google.com2015-09-03 → 2026-07-31 · 2 obs

● 2015-09-03 19:30:16
● 2026-07-31 11:49:18

○MXaspmx2.googlemail.com2015-09-03 → 2016-12-06 · 4 obs

● 2015-09-03 19:30:16
● 2016-12-06 19:43:02
○ 2016-12-23 20:26:20
○ 2026-07-31 11:49:18

○MXaspmx3.googlemail.com2015-09-03 → 2016-12-06 · 4 obs

● 2015-09-03 19:30:16
● 2016-12-06 19:43:02
○ 2016-12-23 20:26:20
○ 2026-07-31 11:49:18

○MXaspmx4.googlemail.com2015-09-03 → 2016-12-06 · 4 obs

● 2015-09-03 19:30:16
● 2016-12-06 19:43:02
○ 2016-12-23 20:26:20
○ 2026-07-31 11:49:18

○MXaspmx5.googlemail.com2015-09-03 → 2016-12-06 · 4 obs

● 2015-09-03 19:30:16
● 2016-12-06 19:43:02
○ 2016-12-23 20:26:20
○ 2026-07-31 11:49:18

○A127.0.0.12017-07-11 → 2017-09-11 · 5 obs

○ 2017-05-30 09:23:04
● 2017-07-11 07:00:34
● 2017-09-11 16:03:30
○ 2026-02-19 19:57:08
○ 2026-07-31 11:49:18

●A188.165.164.1842015-09-03 → 2026-07-31 · 6 obs

● 2015-09-03 19:30:16
● 2016-02-07 08:11:44
○ 2016-02-11 13:37:56
○ 2017-09-11 16:03:30
● 2026-02-19 19:57:08
● 2026-07-31 11:49:18

○A2001:41d0:a:2d23::12015-09-03 → 2015-09-23 · 6 obs

● 2015-09-03 19:30:16
● 2015-09-15 23:29:38
○ 2015-09-16 10:59:00
● 2015-09-23 16:51:38
○ 2015-10-06 20:22:00
○ 2026-07-31 11:49:18

○A216.146.38.702016-02-11 → 2016-12-06 · 5 obs

○ 2016-02-07 08:11:44
● 2016-02-11 13:37:56
● 2016-12-06 19:43:02
○ 2016-12-23 20:26:20
○ 2026-07-31 11:49:18

○A64.182.208.1812016-12-23 → 2017-05-30 · 5 obs

○ 2016-12-06 19:43:02
● 2016-12-23 20:26:20
● 2017-05-30 09:23:04
○ 2017-07-11 07:00:34
○ 2026-07-31 11:49:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
es	a.nic.es, c.nic.es, g.nic.es, h.nic.es	-
ip-addr.es	dns.ip-addr.es, ns.ip-addr.es	2 records

✅ Authoritative Response

Server:91.121.216.105

NS records: dns.ip-addr.es, ns.ip-addr.es

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ip-addr.es (unsigned zone)

⏱️ Timing

Total: 601ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`188.165.164.184`
NS	2	`dns.ip-addr.es, ns.ip-addr.es`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	1	`v=spf1 redirect=_spf.dynamicplus.it`
SOA	1	`ns.ip-addr.es hostmaster.ip-addr.es`

📌 Glue Records Collected

Total: 2

In-bailiwick: 2 (ns.ip-addr.es, dns.ip-addr.es)

Analysis

Hierarchy

The domain ip-addr.es is parent to ns.ip-addr.es, dns.ip-addr.es and www.ip-addr.es.

IP Addresses

ip-addr.es directs to one IP number, which is 188.165.164.184.

Among the host names that share IP numbers with ip-addr.es are vedi.la, kw.gt, ctrl-c.cc and two others.

Name Servers

Two name servers handle the delegation for ip-addr.es: dns.ip-addr.es and ns.ip-addr.es.

Each of dns.ip-addr.es and ns.ip-addr.es has one IP address: dns.ip-addr.es uses 213.251.188.141 and ns.ip-addr.es uses 91.121.216.105.

Mail Servers

Five mail servers handle ip-addr.es: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

ip-addr.es shares at least some of its mail servers with other domains — for example ns500754.ns500754.ns500731.ns500731.ns500688.ns500704.ns500704.ns500291.ns500671.lusty(0x736c7574)z.com, ns500698.ns500698.ns500698.ns500759.ns500736.ns500735.ns500735.ns500708.ns500708.ns500698.ns500576.ns500686.ns500576.ns500619.ns500576.trackreceptor.com, ns500759.ns500698.ns500759.ns500698.ns500735.ns500698.ns500735.ns500736.ns500708.ns500708.ns500698.ns500708.ns500686.ns500652.ns500619.ns500576.trackreceptor.com and two more.

It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.

Hosts with two IP numbers each:

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

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com resolves to two addresses: 74.125.193.27 and 2a00:1450:400b:c01::1b.

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

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