adminwithin.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`adminwithin.com`

DNSSEC	⚠️ Not signed
A	75.2.70.75^{🇺🇸 Amazon75.2.64.0/20}
		PTR	`aacb0a264e514dd48.awsglobalaccelerator.com`
A	99.83.190.102^{🇺🇸 Amazon99.83.176.0/20}
NS	`ns01.domaincontrol.com` ⭐
		A	2603:5:2140::1^{🇺🇸 GODADDY-DNS2603:5:2140::/44}
			PTR	`ns01.domaincontrol.com`
		A	97.74.100.1^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns01.domaincontrol.com`
NS	`ns02.domaincontrol.com`
		A	2603:5:2240::1^{🇺🇸 GODADDY-DNS2603:5:2240::/44}
			PTR	`ns02.domaincontrol.com`
		A	173.201.68.1^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns02.domaincontrol.com`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c06::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bg-in-f26.1e100.net`
		A	2607:f8b0:4004:c06::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bg-in-f27.1e100.net`
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	2607:f8b0:4004:c1b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f27.1e100.net`
		A	64.233.180.26^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-in-f26.1e100.net`
		A	64.233.180.27^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
		A	142.251.179.26^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f26.1e100.net`
		A	172.253.62.27^{🇺🇸 Google172.253.62.0/24}
			PTR	`bc-in-f27.1e100.net`
		A	192.179.24.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`rz-in-f26.1e100.net`
SOA	`ns01.domaincontrol.com`dns@jomax.net 2026-01-22 #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=1793273236

Same first word

adminwithin.com

Previous names

Next names

DNS History

17 records (5 active, 12 former)

○NSns-cloud-e1.googledomains.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 12:09:54
○ 2017-09-15 07:55:10
○ 2026-10-29 12:03:20

○NSns-cloud-e2.googledomains.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 12:09:54
○ 2017-09-15 07:55:10
○ 2026-10-29 12:03:20

○NSns-cloud-e3.googledomains.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 12:09:54
○ 2017-09-15 07:55:10
○ 2026-10-29 12:03:20

○NSns-cloud-e4.googledomains.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 12:09:54
○ 2017-09-15 07:55:10
○ 2026-10-29 12:03:20

●NSns01.domaincontrol.com2026-09-06 → 2026-10-29 · 3 obs

○ 2017-09-15 07:55:10
● 2026-09-06 06:45:56
● 2026-10-29 12:03:20

●NSns02.domaincontrol.com2026-09-06 → 2026-10-29 · 3 obs

○ 2017-09-15 07:55:10
● 2026-09-06 06:45:56
● 2026-10-29 12:03:20

○NSns6.wixdns.net2017-09-15 → 2017-09-15 · 4 obs

○ 2016-12-17 12:09:54
● 2017-09-15 07:55:10
○ 2026-09-06 06:45:56
○ 2026-10-29 12:03:20

○NSns7.wixdns.net2017-09-15 → 2017-09-15 · 4 obs

○ 2016-12-17 12:09:54
● 2017-09-15 07:55:10
○ 2026-09-06 06:45:56
○ 2026-10-29 12:03:20

○MXalt1.aspmx.l.google.com2017-09-15 → 2017-09-15 · 3 obs

● 2017-09-15 07:55:10
○ 2026-09-06 06:45:56
○ 2026-10-29 12:03:20

○MXalt2.aspmx.l.google.com2017-09-15 → 2017-09-15 · 3 obs

● 2017-09-15 07:55:10
○ 2026-09-06 06:45:56
○ 2026-10-29 12:03:20

○MXalt3.aspmx.l.google.com2017-09-15 → 2017-09-15 · 3 obs

● 2017-09-15 07:55:10
○ 2026-09-06 06:45:56
○ 2026-10-29 12:03:20

○MXalt4.aspmx.l.google.com2017-09-15 → 2017-09-15 · 3 obs

● 2017-09-15 07:55:10
○ 2026-09-06 06:45:56
○ 2026-10-29 12:03:20

○MXaspmx.l.google.com2017-09-15 → 2017-09-15 · 3 obs

● 2017-09-15 07:55:10
○ 2026-09-06 06:45:56
○ 2026-10-29 12:03:20

●MXsmtp.google.com2026-09-06 → 2026-10-29 · 3 obs

○ 2017-09-15 07:55:10
● 2026-09-06 06:45:56
● 2026-10-29 12:03:20

○A23.236.62.1472017-09-15 → 2017-09-15 · 3 obs

● 2017-09-15 07:55:10
○ 2026-09-06 06:45:56
○ 2026-10-29 12:03:20

●A75.2.70.752026-09-06 → 2026-10-29 · 3 obs

○ 2017-09-15 07:55:10
● 2026-09-06 06:45:56
● 2026-10-29 12:03:20

●A99.83.190.1022026-09-06 → 2026-10-29 · 3 obs

○ 2017-09-15 07:55:10
● 2026-09-06 06:45:56
● 2026-10-29 12:03:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	d.gtld-servers.net, e.gtld-servers.net, h.gtld-servers.net, b.gtld-servers.net...	-
adminwithin.com	ns01.domaincontrol.com, ns02.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.68.1

NS records: ns01.domaincontrol.com, ns02.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for adminwithin.com (unsigned zone)

⏱️ Timing

Total: 477ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`75.2.70.75, 99.83.190.102`
NS	2	`ns01.domaincontrol.com, ns02.domaincontrol.com`
MX	1	`smtp.google.com (pri: 1)`
SOA	1	`ns01.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns01.domaincontrol.com, ns01.domaincontrol.com, ns02.domaincontrol.com...)

Analysis

IP Addresses

adminwithin.com points to the IP addresses 75.2.70.75 and 99.83.190.102

Two other host names, along with debateplanet.co.uk, dotweblify.pro and nejlaser.cz, also share IP numbers with adminwithin.com.

Name Servers

adminwithin.com is delegated to two name servers: ns01.domaincontrol.com and ns02.domaincontrol.com.

adminwithin.com shares its NS records with other domains, for example thzeroth.com, wallconsultinggroup.us, isismarcondes.com and two others.

adminwithin.com at least partially shares name servers with other domains, for instance tvh.in.

ns01.domaincontrol.com and ns02.domaincontrol.com each resolve to two IP addresses: ns01.domaincontrol.com points to 97.74.100.1 and 2603:5:2140::1, while ns02.domaincontrol.com points to 173.201.68.1 and 2603:5:2240::1.

Mail Servers

The sole mail server for adminwithin.com is smtp.google.com.

With 9 IP addresses total, smtp.google.com resolves to 64.233.180.26, 64.233.180.27, 142.251.179.26 and 6 others.