developingem.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`developingem.com`

DNSSEC	⚠️ Not signed
A	192.0.78.152^{🇺🇸 Automattic192.0.78.0/24 Route Object}
A	192.0.78.232^{🇺🇸 Automattic192.0.78.0/24 Route Object}
NS	`ns1.wordpress.com` ⭐
		A	2a04:fa87:ffff::c6b5:7409^{🇮🇪 Automattic2a04:fa87:ffff::/48}
			PTR	`ns1.wordpress.com`
		A	198.181.116.9^{🇺🇸 Automattic198.181.116.0/24 Route Object}
			PTR	`ns1.wordpress.com`
NS	`ns2.wordpress.com`
		A	2a04:fa87:ffff::c6b5:7509^{🇮🇪 Automattic2a04:fa87:ffff::/48}
			PTR	`ns2.wordpress.com`
		A	198.181.117.9^{🇺🇸 Automattic198.181.117.0/24 Route Object}
			PTR	`ns2.wordpress.com`
NS	`ns3.wordpress.com`
		A	2620:115:c00f::c000:4a09^{🇺🇸 Automattic2620:115:c00f::/48 Route6 Object}
			PTR	`ns3.wordpress.com`
		A	192.0.74.9^{🇺🇸 Automattic192.0.74.0/24 Route Object}
			PTR	`ns3.wordpress.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1d::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f27.1e100.net`
		A	172.253.62.27^{🇺🇸 Google172.253.62.0/24}
			PTR	`bc-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.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`aspmx2.googlemail.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	`aspmx3.googlemail.com`⁽¹⁰⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
TXT	`google-site-verification=R7CBU_0ZZ7R-HXl2JVqVRNRnJL0r85YWrM7ZNBPG4VY`
TXT	`v=spf1 include:aspmx.googlemail.com include:_spf.wpcloud.com ~all`
SOA	`ns1.wordpress.com`hostmaster@wordpress.com 2005-07-18 #58

`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=1788832968

Same first word

developingem.com

Similar names

developingme.com

Previous names

Next names

DNS History

12 records (10 active, 2 former)

●NSns1.wordpress.com2015-08-15 → 2026-09-08 · 2 obs

● 2015-08-15 05:12:48
● 2026-09-08 02:11:26

●NSns2.wordpress.com2015-08-15 → 2026-09-08 · 2 obs

● 2015-08-15 05:12:48
● 2026-09-08 02:11:26

●NSns3.wordpress.com2015-08-15 → 2026-09-08 · 2 obs

● 2015-08-15 05:12:48
● 2026-09-08 02:11:26

●MXalt1.aspmx.l.google.com2015-08-15 → 2026-09-08 · 2 obs

● 2015-08-15 05:12:48
● 2026-09-08 02:11:26

●MXalt2.aspmx.l.google.com2015-08-15 → 2026-09-08 · 2 obs

● 2015-08-15 05:12:48
● 2026-09-08 02:11:26

●MXaspmx.l.google.com2015-08-15 → 2026-09-08 · 2 obs

● 2015-08-15 05:12:48
● 2026-09-08 02:11:26

●MXaspmx2.googlemail.com2015-08-15 → 2026-09-08 · 2 obs

● 2015-08-15 05:12:48
● 2026-09-08 02:11:26

●MXaspmx3.googlemail.com2015-08-15 → 2026-09-08 · 2 obs

● 2015-08-15 05:12:48
● 2026-09-08 02:11:26

●A192.0.78.1522026-09-04 → 2026-09-08 · 3 obs

○ 2018-08-05 15:19:56
● 2026-09-04 23:54:52
● 2026-09-08 02:11:26

●A192.0.78.2322026-09-04 → 2026-09-08 · 3 obs

○ 2018-08-05 15:19:56
● 2026-09-04 23:54:52
● 2026-09-08 02:11:26

○A192.0.78.242015-08-15 → 2018-08-05 · 4 obs

● 2015-08-15 05:12:48
● 2018-08-05 15:19:56
○ 2026-09-04 23:54:52
○ 2026-09-08 02:11:26

○A192.0.78.252015-08-15 → 2018-08-05 · 4 obs

● 2015-08-15 05:12:48
● 2018-08-05 15:19:56
○ 2026-09-04 23:54:52
○ 2026-09-08 02:11:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
developingem.com	ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com	6 records

✅ Authoritative Response

Server:198.181.116.9

NS records: ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for developingem.com (unsigned zone)

⏱️ Timing

Total: 1199ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`192.0.78.232, 192.0.78.152`
NS	3	`ns3.wordpress.com, ns2.wordpress.com...`
MX	5	`alt2.aspmx.l.google.com (pri: 5), alt1.aspmx.l.google.com (pri: 5)...`
TXT	2	`v=spf1 include:aspmx.googlemail.com incl, google-site-verification=R7CBU_0ZZ7R-HXl`
SOA	1	`ns1.wordpress.com hostmaster.wordpress.c`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns1.wordpress.com, ns1.wordpress.com, ns2.wordpress.com...)

Analysis

IP Addresses

developingem.com resolves to the IP addresses 192.0.78.152 and 192.0.78.232

lacasa.company, delautor.com, atv.fi and two other host names share IP numbers with developingem.com.

Name Servers

The authoritative name servers for developingem.com are ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com — three in total.

developingem.com shares at least some of its name servers with other domains, including divirtase.curitiba.br, ewmigration.com, lessthan1000followers.com and two others.

ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com all resolve to exactly two IP numbers apiece: ns1.wordpress.com → 198.181.116.9 and 2a04:fa87:ffff::c6b5:7409; ns2.wordpress.com → 198.181.117.9 and 2a04:fa87:ffff::c6b5:7509; ns3.wordpress.com → 192.0.74.9 and 2620:115:c00f::c000:4a09.

Mail Servers

developingem.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

developingem.com has at least partial mail server overlap with other domains such as courseday.com, lundcomm.in, getuhoo.com and two more.

These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.

Hostnames that resolve to two IP addresses:

aspmx2.googlemail.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1b.

aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.

aspmx.l.google.com directs traffic to 172.253.62.27 and 2607:f8b0:4004:c1d::1b.

alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c14::1b IP addresses each.

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