securecomponents.com - dns.ninja

`securecomponents.com`

DNSSEC	⚠️ Not signed
A	35.212.6.98^{🇺🇸 Google35.212.0.0/17}
		PTR	`98.6.212.35.bc.googleusercontent.com`
NS	`ns11.domaincontrol.com` ⭐
		A	2603:5:2190::6^{🇺🇸 GODADDY-DNS2603:5:2190::/44}
			PTR	`ns11.domaincontrol.com`
		A	97.74.105.6^{🇺🇸 GODADDY-DNS97.74.104.0/23}
			PTR	`ns11.domaincontrol.com`
NS	`ns12.domaincontrol.com`
		A	2603:5:2290::6^{🇺🇸 GODADDY-DNS2603:5:2290::/44}
			PTR	`ns12.domaincontrol.com`
		A	173.201.73.6^{🇺🇸 GODADDY-DNS173.201.72.0/23}
			PTR	`ns12.domaincontrol.com`
MX	`mx1-us1.ppe-hosted.com` ⭐
		A	67.231.154.162^{🇺🇸 Proofpoint67.231.154.0/24 Inc.}
			PTR	`mx1-us1.ppe-hosted.com`
		A	148.163.129.50^{🇺🇸 AS13916148.163.129.0/24 Proofpoint Inc.}
			PTR	`mx1-us1.ppe-hosted.com`
MX	`mx2-us1.ppe-hosted.com`⁽²⁰⁾
		A	67.231.154.163^{🇺🇸 Proofpoint67.231.154.0/24 Inc.}
			PTR	`mx2-us1.ppe-hosted.com`
		A	148.163.129.51^{🇺🇸 AS13916148.163.129.0/24 Proofpoint Inc.}
			PTR	`mx2-us1.ppe-hosted.com`
TXT	`v=spf1 include:_spf.securecomponents_com._d.easydmarc.pro ~all`
TXT	`ppe-308a8b6651725921d815dcb4bdb3b839851c7eb1`
TXT	`MS=ms41401426`
TXT	`apple-domain-verification=dTKokNVqs8W0OMN3`
TXT	`google-site-verification=VEDpObYc7RMiwaaytO0bqgWXCsFDoLCwPTsi20WYzbc`
SOA	`ns11.domaincontrol.com`dns@jomax.net 2025-11-20 #0

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

Subdomains

blog.securecomponents.com

Same first word

securecomponents.com

DNS History

23 records (5 active, 18 former)

○NSdns1.name-services.com2008-03-06 → 2008-03-06 · 3 obs

● 2008-03-06 19:22:08
○ 2015-08-17 00:06:14
○ 2026-06-30 20:34:58

○NSdns2.name-services.com2008-03-06 → 2008-03-06 · 3 obs

● 2008-03-06 19:22:08
○ 2015-08-17 00:06:14
○ 2026-06-30 20:34:58

○NSdns3.name-services.com2008-03-06 → 2008-03-06 · 3 obs

● 2008-03-06 19:22:08
○ 2015-08-17 00:06:14
○ 2026-06-30 20:34:58

○NSdns4.name-services.com2008-03-06 → 2008-03-06 · 3 obs

● 2008-03-06 19:22:08
○ 2015-08-17 00:06:14
○ 2026-06-30 20:34:58

○NSdns5.name-services.com2008-03-06 → 2008-03-06 · 3 obs

● 2008-03-06 19:22:08
○ 2015-08-17 00:06:14
○ 2026-06-30 20:34:58

○NSns1.websitehostserver.net2015-08-17 → 2017-04-19 · 5 obs

○ 2008-03-06 19:22:08
● 2015-08-17 00:06:14
● 2017-04-19 04:30:10
○ 2026-03-23 02:20:26
○ 2026-06-30 20:34:58

●NSns11.domaincontrol.com2026-03-23 → 2026-06-30 · 3 obs

○ 2017-04-19 04:30:10
● 2026-03-23 02:20:26
● 2026-06-30 20:34:58

●NSns12.domaincontrol.com2026-03-23 → 2026-06-30 · 3 obs

○ 2017-04-19 04:30:10
● 2026-03-23 02:20:26
● 2026-06-30 20:34:58

○NSns2.websitehostserver.net2015-08-17 → 2017-04-19 · 5 obs

○ 2008-03-06 19:22:08
● 2015-08-17 00:06:14
● 2017-04-19 04:30:10
○ 2026-03-23 02:20:26
○ 2026-06-30 20:34:58

○MXalt1.aspmx.l.google.com2008-03-06 → 2017-04-19 · 4 obs

● 2008-03-06 19:22:08
● 2017-04-19 04:30:10
○ 2026-03-23 02:20:26
○ 2026-06-30 20:34:58

○MXalt2.aspmx.l.google.com2008-03-06 → 2017-04-19 · 4 obs

● 2008-03-06 19:22:08
● 2017-04-19 04:30:10
○ 2026-03-23 02:20:26
○ 2026-06-30 20:34:58

○MXaspmx.l.google.com2008-03-06 → 2017-04-19 · 4 obs

● 2008-03-06 19:22:08
● 2017-04-19 04:30:10
○ 2026-03-23 02:20:26
○ 2026-06-30 20:34:58

○MXaspmx2.googlemail.com2008-03-06 → 2017-04-19 · 4 obs

● 2008-03-06 19:22:08
● 2017-04-19 04:30:10
○ 2026-03-23 02:20:26
○ 2026-06-30 20:34:58

○MXaspmx3.googlemail.com2008-03-06 → 2017-04-19 · 4 obs

● 2008-03-06 19:22:08
● 2017-04-19 04:30:10
○ 2026-03-23 02:20:26
○ 2026-06-30 20:34:58

○MXaspmx4.googlemail.com2008-03-06 → 2017-04-19 · 4 obs

● 2008-03-06 19:22:08
● 2017-04-19 04:30:10
○ 2026-03-23 02:20:26
○ 2026-06-30 20:34:58

○MXaspmx5.googlemail.com2008-03-06 → 2017-04-19 · 4 obs

● 2008-03-06 19:22:08
● 2017-04-19 04:30:10
○ 2026-03-23 02:20:26
○ 2026-06-30 20:34:58

●MXmx1-us1.ppe-hosted.com2026-03-23 → 2026-06-30 · 3 obs

○ 2017-04-19 04:30:10
● 2026-03-23 02:20:26
● 2026-06-30 20:34:58

●MXmx2-us1.ppe-hosted.com2026-03-23 → 2026-06-30 · 3 obs

○ 2017-04-19 04:30:10
● 2026-03-23 02:20:26
● 2026-06-30 20:34:58

○A184.154.164.2022015-08-17 → 2017-04-19 · 5 obs

○ 2008-03-06 19:22:08
● 2015-08-17 00:06:14
● 2017-04-19 04:30:10
○ 2026-03-23 02:20:26
○ 2026-06-30 20:34:58

●A35.212.6.982026-03-23 → 2026-06-30 · 3 obs

○ 2017-04-19 04:30:10
● 2026-03-23 02:20:26
● 2026-06-30 20:34:58

○A64.233.179.1212008-03-06 → 2008-03-06 · 3 obs

● 2008-03-06 19:22:08
○ 2015-08-17 00:06:14
○ 2026-06-30 20:34:58

○A66.249.81.1212008-03-06 → 2008-03-06 · 3 obs

● 2008-03-06 19:22:08
○ 2015-08-17 00:06:14
○ 2026-06-30 20:34:58

○A72.14.207.1212008-03-06 → 2008-03-06 · 3 obs

● 2008-03-06 19:22:08
○ 2015-08-17 00:06:14
○ 2026-06-30 20:34:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, a.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
securecomponents.com	ns11.domaincontrol.com, ns12.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.105.6

NS records: ns11.domaincontrol.com, ns12.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for securecomponents.com (unsigned zone)

⏱️ Timing

Total: 195ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`35.212.6.98`
NS	2	`ns11.domaincontrol.com, ns12.domaincontrol.com`
MX	2	`mx1-us1.ppe-hosted.com (pri: 10), mx2-us1.ppe-hosted.com (pri: 20)`
TXT	5	`v=spf1 include:_spf.securecomponents_com, ppe-308a8b6651725921d815dcb4bdb3b839851c...`
SOA	1	`ns11.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns11.domaincontrol.com, ns11.domaincontrol.com, ns12.domaincontrol.com...)

Analysis

Hierarchy

securecomponents.com serves as the parent of blog.securecomponents.com.

IP Addresses

securecomponents.com points to a single IP number: 35.212.6.98.

Additional host names — gilgai.com, necoem.org, www.vacantespanama.com and two others — share IP numbers with securecomponents.com.

Name Servers

The NS records for securecomponents.com delegate to ns11.domaincontrol.com and ns12.domaincontrol.com.

securecomponents.com shares its name server setup with other domains, including hvrealestatecareers.com, brandingagencyseattle.com, rosstas.com and two others.

securecomponents.com and other domains like cl-asi.org share at least a portion of their name servers.

ns11.domaincontrol.com resolves to 97.74.105.6 and 2603:5:2190::6. Likewise, ns12.domaincontrol.com resolves to 173.201.73.6 and 2603:5:2290::6 — two IP addresses apiece.

Mail Servers

securecomponents.com has two mail servers: mx1-us1.ppe-hosted.com and mx2-us1.ppe-hosted.com.

securecomponents.com shares the same mail server setup as other domains, including rushlawberks.com, bonfigliobuilders.com, fireflybrandmanagement.com and two others.

securecomponents.com shares mail servers — at least in part — with other domains, including wonthaggimedical.com.au, mvragency.com, lmwi.pro and two others.

mx1-us1.ppe-hosted.com resolves to 67.231.154.162 and 148.163.129.50. Likewise, mx2-us1.ppe-hosted.com resolves to 67.231.154.163 and 148.163.129.51 — two IP addresses apiece.