rodgersengineering.com - dns.ninja

`rodgersengineering.com`

DNSSEC	⚠️ Not signed
A	3.33.130.190^{🇺🇸 Amazon3.33.128.0/20}
A	15.197.148.33^{🇺🇸 Amazon15.197.144.0/20}
NS	`ns59.domaincontrol.com` ⭐
		A	2603:5:2143::1f^{🇺🇸 GODADDY-DNS2603:5:2140::/44}
			PTR	`mns01.domaincontrol.com`
		A	97.74.100.31^{🇺🇸 GODADDY-DNS97.74.100.0/23}
NS	`ns60.domaincontrol.com`
		A	2603:5:2243::1f^{🇺🇸 GODADDY-DNS2603:5:2240::/44}
			PTR	`mns02.domaincontrol.com`
		A	173.201.68.31^{🇺🇸 GODADDY-DNS173.201.68.0/23}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c25::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadtq-in-f27.1e100.net`
		A	142.251.16.26^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.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}
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.26^{🇺🇸 Google192.178.223.0/24}
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
SOA	`ns59.domaincontrol.com`dns@jomax.net 2026-03-11 #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=1782687010

WOT: SAFE (68/100)

Same first word

rodgersengineering.com

DNS History

22 records (9 active, 13 former)

○NSns1.m40.siteground.biz2017-08-17 → 2017-08-17 · 4 obs

○ 2016-11-27 07:04:58
● 2017-08-17 06:01:34
○ 2026-02-22 20:38:00
○ 2026-06-28 23:15:14

○NSns1.siteground.net2026-02-22 → 2026-02-22 · 4 obs

○ 2017-08-17 06:01:34
● 2026-02-22 20:38:00
○ 2026-03-02 19:21:08
○ 2026-06-28 23:15:14

○NSns1.us125.siteground.us2026-02-22 → 2026-03-02 · 5 obs

○ 2017-08-17 06:01:34
● 2026-02-22 20:38:00
● 2026-03-02 19:21:08
○ 2026-04-14 07:55:22
○ 2026-06-28 23:15:14

○NSns2.m40.siteground.biz2017-08-17 → 2017-08-17 · 4 obs

○ 2016-11-27 07:04:58
● 2017-08-17 06:01:34
○ 2026-02-22 20:38:00
○ 2026-06-28 23:15:14

○NSns2.siteground.net2026-02-22 → 2026-02-22 · 4 obs

○ 2017-08-17 06:01:34
● 2026-02-22 20:38:00
○ 2026-03-02 19:21:08
○ 2026-06-28 23:15:14

○NSns2.us125.siteground.us2026-02-22 → 2026-03-02 · 5 obs

○ 2017-08-17 06:01:34
● 2026-02-22 20:38:00
● 2026-03-02 19:21:08
○ 2026-04-14 07:55:22
○ 2026-06-28 23:15:14

○NSns57.domaincontrol.com2016-11-27 → 2016-11-27 · 3 obs

● 2016-11-27 07:04:58
○ 2017-08-17 06:01:34
○ 2026-06-28 23:15:14

○NSns58.domaincontrol.com2016-11-27 → 2016-11-27 · 3 obs

● 2016-11-27 07:04:58
○ 2017-08-17 06:01:34
○ 2026-06-28 23:15:14

●NSns59.domaincontrol.com2026-04-14 → 2026-06-28 · 3 obs

○ 2026-03-02 19:21:08
● 2026-04-14 07:55:22
● 2026-06-28 23:15:14

●NSns60.domaincontrol.com2026-04-14 → 2026-06-28 · 3 obs

○ 2026-03-02 19:21:08
● 2026-04-14 07:55:22
● 2026-06-28 23:15:14

●MXalt1.aspmx.l.google.com2017-08-17 → 2026-06-28 · 6 obs

○ 2016-11-27 07:04:58
● 2017-08-17 06:01:34
● 2026-02-22 20:38:00
○ 2026-03-02 19:21:08
● 2026-04-14 07:55:22
● 2026-06-28 23:15:14

●MXalt2.aspmx.l.google.com2017-08-17 → 2026-06-28 · 6 obs

○ 2016-11-27 07:04:58
● 2017-08-17 06:01:34
● 2026-02-22 20:38:00
○ 2026-03-02 19:21:08
● 2026-04-14 07:55:22
● 2026-06-28 23:15:14

●MXalt3.aspmx.l.google.com2017-08-17 → 2026-06-28 · 6 obs

○ 2016-11-27 07:04:58
● 2017-08-17 06:01:34
● 2026-02-22 20:38:00
○ 2026-03-02 19:21:08
● 2026-04-14 07:55:22
● 2026-06-28 23:15:14

●MXalt4.aspmx.l.google.com2017-08-17 → 2026-06-28 · 6 obs

○ 2016-11-27 07:04:58
● 2017-08-17 06:01:34
● 2026-02-22 20:38:00
○ 2026-03-02 19:21:08
● 2026-04-14 07:55:22
● 2026-06-28 23:15:14

●MXaspmx.l.google.com2017-08-17 → 2026-06-28 · 6 obs

○ 2016-11-27 07:04:58
● 2017-08-17 06:01:34
● 2026-02-22 20:38:00
○ 2026-03-02 19:21:08
● 2026-04-14 07:55:22
● 2026-06-28 23:15:14

○MXmailstore1.secureserver.net2016-11-27 → 2016-11-27 · 3 obs

● 2016-11-27 07:04:58
○ 2017-08-17 06:01:34
○ 2026-06-28 23:15:14

○MXsmtp.secureserver.net2016-11-27 → 2016-11-27 · 3 obs

● 2016-11-27 07:04:58
○ 2017-08-17 06:01:34
○ 2026-06-28 23:15:14

●A15.197.148.332026-04-14 → 2026-06-28 · 3 obs

○ 2026-03-02 19:21:08
● 2026-04-14 07:55:22
● 2026-06-28 23:15:14

○A185.56.85.1112017-08-17 → 2017-08-17 · 4 obs

○ 2016-11-27 07:04:58
● 2017-08-17 06:01:34
○ 2026-02-22 20:38:00
○ 2026-06-28 23:15:14

●A3.33.130.1902026-04-14 → 2026-06-28 · 3 obs

○ 2026-03-02 19:21:08
● 2026-04-14 07:55:22
● 2026-06-28 23:15:14

○A35.215.74.422026-02-22 → 2026-02-22 · 4 obs

○ 2017-08-17 06:01:34
● 2026-02-22 20:38:00
○ 2026-03-02 19:21:08
○ 2026-06-28 23:15:14

○A50.63.202.492016-11-27 → 2016-11-27 · 3 obs

● 2016-11-27 07:04:58
○ 2017-08-17 06:01:34
○ 2026-06-28 23:15:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
rodgersengineering.com	ns59.domaincontrol.com, ns60.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.68.31

NS records: ns59.domaincontrol.com, ns60.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for rodgersengineering.com (unsigned zone)

⏱️ Timing

Total: 346ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`3.33.130.190, 15.197.148.33`
NS	2	`ns59.domaincontrol.com, ns60.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
SOA	1	`ns59.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns59.domaincontrol.com, ns59.domaincontrol.com, ns60.domaincontrol.com...)

Analysis

IP Addresses

rodgersengineering.com has two IP addresses: 3.33.130.190 and 15.197.148.33

cashflo.in, palsouq.com, minicaddie.com and two other host names share IP numbers with rodgersengineering.com.

Name Servers

Two name servers handle the delegation for rodgersengineering.com: ns59.domaincontrol.com and ns60.domaincontrol.com.

rodgersengineering.com uses the same name servers as several other domains — among them milcohort.com, doporto.mx, tektoniks.net and two more.

rodgersengineering.com is at least partially co-delegated on name servers with other domains, such as swiftparts.com.

ns59.domaincontrol.com and ns60.domaincontrol.com both carry two IP addresses. The A records for ns59.domaincontrol.com are 97.74.100.31 and 2603:5:2143::1f; the A records for ns60.domaincontrol.com are 173.201.68.31 and 2603:5:2243::1f.

Mail Servers

Five mail servers handle rodgersengineering.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

rodgersengineering.com has at least partial mail server overlap with other domains such as pttjs.id, imfresh.com.br, ns500599.ns500737.ns500599.ns500737.ns500599.ns500724.ns500724.ns500724.ns500583.ns500697.ns500697.ns500583.yummyflingsfinder.com and two more.

These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com resolves to two addresses: 142.251.16.26 and 2607:f8b0:4004:c25::1b.

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

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

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

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