nodegamers.com - dns.ninja

`nodegamers.com`

DNSSEC	⚠️ Not signed
A	192.0.78.144^{🇺🇸 Automattic192.0.78.0/24 Route Object}
A	192.0.78.219^{🇺🇸 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	`mx1.titan.email` ⭐
		A	3.230.80.41^{🇺🇸 Amazon3.224.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-230-80-41.compute-1.amazonaws.com`
		A	23.21.108.1^{🇺🇸 Amazon23.20.0.0/15 EC2 IAD prefix}
			PTR	`ec2-23-21-108-1.compute-1.amazonaws.com`
		A	98.85.38.42^{🇺🇸 Amazon98.80.0.0/13 EC2 IAD Prefix}
			PTR	`ec2-98-85-38-42.compute-1.amazonaws.com`
MX	`mx2.titan.email`⁽²⁰⁾
		A	3.230.80.41^{🇺🇸 Amazon3.224.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-230-80-41.compute-1.amazonaws.com`
		A	23.21.108.1^{🇺🇸 Amazon23.20.0.0/15 EC2 IAD prefix}
			PTR	`ec2-23-21-108-1.compute-1.amazonaws.com`
		A	98.85.38.42^{🇺🇸 Amazon98.80.0.0/13 EC2 IAD Prefix}
			PTR	`ec2-98-85-38-42.compute-1.amazonaws.com`
TXT	`v=spf1 include:spf.titan.email 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=1781444460

Subdomains

mail.nodegamers.com

Same first word

nodegamers.com

Similar names

DNS History

9 records (7 active, 2 former)

●NSns1.wordpress.com2026-04-08 → 2026-06-14 · 2 obs

● 2026-04-08 14:52:44
● 2026-06-14 13:44:10

●NSns2.wordpress.com2026-04-08 → 2026-06-14 · 2 obs

● 2026-04-08 14:52:44
● 2026-06-14 13:44:10

●NSns3.wordpress.com2026-04-08 → 2026-06-14 · 2 obs

● 2026-04-08 14:52:44
● 2026-06-14 13:44:10

●MXmx1.titan.email2026-04-08 → 2026-06-14 · 2 obs

● 2026-04-08 14:52:44
● 2026-06-14 13:44:10

●MXmx2.titan.email2026-04-08 → 2026-06-14 · 2 obs

● 2026-04-08 14:52:44
● 2026-06-14 13:44:10

●A192.0.78.1442026-06-13 → 2026-06-14 · 3 obs

○ 2026-05-30 23:51:06
● 2026-06-13 17:40:36
● 2026-06-14 13:44:10

●A192.0.78.2192026-06-13 → 2026-06-14 · 3 obs

○ 2026-05-30 23:51:06
● 2026-06-13 17:40:36
● 2026-06-14 13:44:10

○A192.0.78.242026-04-08 → 2026-05-30 · 4 obs

● 2026-04-08 14:52:44
● 2026-05-30 23:51:06
○ 2026-06-13 17:40:36
○ 2026-06-14 13:44:10

○A192.0.78.252026-04-08 → 2026-05-30 · 4 obs

● 2026-04-08 14:52:44
● 2026-05-30 23:51:06
○ 2026-06-13 17:40:36
○ 2026-06-14 13:44:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, e.gtld-servers.net, g.gtld-servers.net, k.gtld-servers.net...	-
nodegamers.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 nodegamers.com (unsigned zone)

⏱️ Timing

Total: 266ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`192.0.78.219, 192.0.78.144`
NS	3	`ns3.wordpress.com, ns2.wordpress.com...`
MX	2	`mx2.titan.email (pri: 20), mx1.titan.email (pri: 10)`
TXT	1	`v=spf1 include:spf.titan.email include:_`
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

Hierarchy

nodegamers.com is a parent domain of mail.nodegamers.com.

IP Addresses

nodegamers.com resolves to the IP addresses 192.0.78.144 and 192.0.78.219

Two other host names, along with myhearingplus.com, southwaltoncc.org and email.vilni-media.com, also share IP numbers with nodegamers.com.

Name Servers

DNS for nodegamers.com is handled by three authoritative name servers: ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com.

nodegamers.com shares at least some of its name servers with other domains, including adityakane.com, sagesmicrofarm.com., designgenesis.com.br and two others.

Three hostnames — ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com — each have two IP addresses: ns1.wordpress.com has 198.181.116.9 and 2a04:fa87:ffff::c6b5:7409, ns2.wordpress.com has 198.181.117.9 and 2a04:fa87:ffff::c6b5:7509, and ns3.wordpress.com has 192.0.74.9 and 2620:115:c00f::c000:4a09.

Mail Servers

nodegamers.com is served by two mail servers, mx1.titan.email and mx2.titan.email.

Among the domains sharing a mail server setup with nodegamers.com are movies-hd.club, bravacursos.com.br, afconbmx.com and two others.

There is at least a partial MX overlap between nodegamers.com and other domains, including arwauniversity.edu.ye, cooltour.com.mx, knitura.com and two others.

mx1.titan.email resolves to 3.230.80.41, 23.21.108.1 and 98.85.38.42; mx2.titan.email resolves to those same three IP addresses.

Host names pointing to 3.230.80.41 IP addresses: mx1.titan.email and mx2.titan.email.

Host names pointing to 23.21.108.1 IP addresses: mx1.titan.email and mx2.titan.email.

Host names pointing to 98.85.38.42 IP addresses: mx1.titan.email and mx2.titan.email.