imasingle.com - dns.ninja

`imasingle.com`

DNSSEC	⚠️ Not signed
A	3.33.251.168^{🇺🇸 Amazon3.33.240.0/20}
		PTR	`aec037177372cc6cd.awsglobalaccelerator.com`
A	15.197.225.128^{🇺🇸 Amazon15.197.224.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`
SOA	`ns01.domaincontrol.com`dns@jomax.net 2026-08-03 #3

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

Same first word

imasingle.com

Similar names

DNS History

20 records (4 active, 16 former)

○NScpns01.secureserver.net2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 19:26:04
○ 2015-11-02 23:34:04
○ 2026-08-14 06:15:54

○NScpns02.secureserver.net2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 19:26:04
○ 2015-11-02 23:34:04
○ 2026-08-14 06:15:54

○NSdns1.registrar-servers.com2016-04-20 → 2017-03-24 · 5 obs

○ 2015-11-02 23:34:04
● 2016-04-20 04:22:58
● 2017-03-24 09:17:48
○ 2026-03-16 03:38:40
○ 2026-08-14 06:15:54

○NSdns2.registrar-servers.com2016-04-20 → 2017-03-24 · 5 obs

○ 2015-11-02 23:34:04
● 2016-04-20 04:22:58
● 2017-03-24 09:17:48
○ 2026-03-16 03:38:40
○ 2026-08-14 06:15:54

○NSdns3.registrar-servers.com2016-04-20 → 2017-03-24 · 5 obs

○ 2015-11-02 23:34:04
● 2016-04-20 04:22:58
● 2017-03-24 09:17:48
○ 2026-03-16 03:38:40
○ 2026-08-14 06:15:54

○NSdns4.registrar-servers.com2016-04-20 → 2017-03-24 · 5 obs

○ 2015-11-02 23:34:04
● 2016-04-20 04:22:58
● 2017-03-24 09:17:48
○ 2026-03-16 03:38:40
○ 2026-08-14 06:15:54

○NSdns5.registrar-servers.com2016-04-20 → 2017-03-24 · 5 obs

○ 2015-11-02 23:34:04
● 2016-04-20 04:22:58
● 2017-03-24 09:17:48
○ 2026-03-16 03:38:40
○ 2026-08-14 06:15:54

●NSns01.domaincontrol.com2026-03-16 → 2026-08-14 · 3 obs

○ 2017-03-24 09:17:48
● 2026-03-16 03:38:40
● 2026-08-14 06:15:54

●NSns02.domaincontrol.com2026-03-16 → 2026-08-14 · 3 obs

○ 2017-03-24 09:17:48
● 2026-03-16 03:38:40
● 2026-08-14 06:15:54

○MXeforward1.registrar-servers.com2016-04-20 → 2017-03-24 · 5 obs

○ 2015-11-02 23:34:04
● 2016-04-20 04:22:58
● 2017-03-24 09:17:48
○ 2026-03-16 03:38:40
○ 2026-08-14 06:15:54

○MXeforward2.registrar-servers.com2016-04-20 → 2017-03-24 · 5 obs

○ 2015-11-02 23:34:04
● 2016-04-20 04:22:58
● 2017-03-24 09:17:48
○ 2026-03-16 03:38:40
○ 2026-08-14 06:15:54

○MXeforward3.registrar-servers.com2016-04-20 → 2017-03-24 · 5 obs

○ 2015-11-02 23:34:04
● 2016-04-20 04:22:58
● 2017-03-24 09:17:48
○ 2026-03-16 03:38:40
○ 2026-08-14 06:15:54

○MXeforward4.registrar-servers.com2016-04-20 → 2017-03-24 · 5 obs

○ 2015-11-02 23:34:04
● 2016-04-20 04:22:58
● 2017-03-24 09:17:48
○ 2026-03-16 03:38:40
○ 2026-08-14 06:15:54

○MXeforward5.registrar-servers.com2016-04-20 → 2017-03-24 · 5 obs

○ 2015-11-02 23:34:04
● 2016-04-20 04:22:58
● 2017-03-24 09:17:48
○ 2026-03-16 03:38:40
○ 2026-08-14 06:15:54

○MXmailstore1.secureserver.net2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 19:26:04
○ 2015-11-02 23:34:04
○ 2026-08-14 06:15:54

○MXsmtp.secureserver.net2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 19:26:04
○ 2015-11-02 23:34:04
○ 2026-08-14 06:15:54

●A15.197.225.1282026-03-16 → 2026-08-14 · 3 obs

○ 2017-03-24 09:17:48
● 2026-03-16 03:38:40
● 2026-08-14 06:15:54

○A162.255.119.2492016-04-20 → 2017-03-24 · 5 obs

○ 2015-11-02 23:34:04
● 2016-04-20 04:22:58
● 2017-03-24 09:17:48
○ 2026-03-16 03:38:40
○ 2026-08-14 06:15:54

●A3.33.251.1682026-03-16 → 2026-08-14 · 3 obs

○ 2017-03-24 09:17:48
● 2026-03-16 03:38:40
● 2026-08-14 06:15:54

○A68.178.232.1432008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 19:26:04
○ 2015-11-02 23:34:04
○ 2026-08-14 06:15:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, m.gtld-servers.net, l.gtld-servers.net, b.gtld-servers.net...	-
imasingle.com	ns01.domaincontrol.com, ns02.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.100.1

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for imasingle.com (unsigned zone)

⏱️ Timing

Total: 283ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`15.197.225.128, 3.33.251.168`
NS	2	`ns01.domaincontrol.com, ns02.domaincontrol.com`
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

imasingle.com resolves to the IP addresses 3.33.251.168 and 15.197.225.128

Among the host names that share IP numbers with imasingle.com are awningsinbocaraton.com, skylerspringstun.com, robinsonmetal.com and two others.

Name Servers

imasingle.com is served by two delegated name servers, ns01.domaincontrol.com and ns02.domaincontrol.com.

imasingle.com has the same name server delegation as a number of other domains, such as yalindanismanlik.net, mooseplate.net, 14pinnacleridge.com and two more.

The DNS delegation for imasingle.com at least partly coincides with that of other domains, fayettevillear.com being one example.

Each of the two host names carries two IP addresses: ns01.domaincontrol.com points to 97.74.100.1 and 2603:5:2140::1, and ns02.domaincontrol.com points to 173.201.68.1 and 2603:5:2240::1.