`wasabiginger.com`

DNSSEC	⚠️ Not signed
A	3.33.224.147^{🇺🇸 Amazon3.33.224.0/20}
		PTR	`ad335c4aa70861008.awsglobalaccelerator.com`
NS	`ns1.aftermarket.com` ⭐
		A	2600:1f16:529:db01::53^{🇺🇸 Amazon2600:1f16:400::/38 AMAZON AWS}
		A	3.141.121.8^{🇺🇸 Amazon3.136.0.0/13 EC2 CMH prefix}
			PTR	`ns1.aftermarket.com`
NS	`ns2.aftermarket.com`
		A	2600:1f16:529:db00::53^{🇺🇸 Amazon2600:1f16:400::/38 AMAZON AWS}
		A	3.15.73.134^{🇺🇸 Amazon3.14.0.0/15 EC2 CMH prefix}
			PTR	`ns2.aftermarket.com`
TXT	`afternic-verification-JMjLoGwNMDdPQhcrfwSwSD`
TXT	`f3af70b58684e0327b1544d7df12105d97e51ed6`
SOA	`ns1.aftermarket.com`support@aftermarket.com 2026-05-07 #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=1778321851

Same first word

wasabiginger.com

Similar names

gingerwasabi.com

DNS History

23 records (3 active, 20 former)

○NSalgin.ns.cloudflare.com2018-11-16 → 2018-11-16 · 4 obs

○ 2016-02-10 07:28:58
● 2018-11-16 20:31:38
○ 2026-02-27 16:10:50
○ 2026-05-09 10:37:22

○NSetta.ns.cloudflare.com2018-11-16 → 2018-11-16 · 4 obs

○ 2016-02-10 07:28:58
● 2018-11-16 20:31:38
○ 2026-02-27 16:10:50
○ 2026-05-09 10:37:22

●NSns1.aftermarket.com2026-02-27 → 2026-05-09 · 3 obs

○ 2018-11-16 20:31:38
● 2026-02-27 16:10:50
● 2026-05-09 10:37:22

○NSns1.dnslink.com2015-06-14 → 2015-06-14 · 3 obs

● 2015-06-14 01:37:48
○ 2015-11-19 14:07:04
○ 2026-05-09 10:37:22

●NSns2.aftermarket.com2026-02-27 → 2026-05-09 · 3 obs

○ 2018-11-16 20:31:38
● 2026-02-27 16:10:50
● 2026-05-09 10:37:22

○NSns2.dnslink.com2015-06-14 → 2015-06-14 · 3 obs

● 2015-06-14 01:37:48
○ 2015-11-19 14:07:04
○ 2026-05-09 10:37:22

○NSns77.domaincontrol.com2015-11-19 → 2015-11-19 · 4 obs

○ 2015-06-14 01:37:48
● 2015-11-19 14:07:04
○ 2016-02-10 07:28:58
○ 2026-05-09 10:37:22

○NSns78.domaincontrol.com2015-11-19 → 2015-11-19 · 4 obs

○ 2015-06-14 01:37:48
● 2015-11-19 14:07:04
○ 2016-02-10 07:28:58
○ 2026-05-09 10:37:22

○MXalt1.aspmx.l.google.com2018-11-16 → 2018-11-16 · 4 obs

○ 2016-02-10 07:28:58
● 2018-11-16 20:31:38
○ 2026-02-27 16:10:50
○ 2026-05-09 10:37:22

○MXalt2.aspmx.l.google.com2018-11-16 → 2018-11-16 · 4 obs

○ 2016-02-10 07:28:58
● 2018-11-16 20:31:38
○ 2026-02-27 16:10:50
○ 2026-05-09 10:37:22

○MXalt3.aspmx.l.google.com2018-11-16 → 2018-11-16 · 4 obs

○ 2016-02-10 07:28:58
● 2018-11-16 20:31:38
○ 2026-02-27 16:10:50
○ 2026-05-09 10:37:22

○MXalt4.aspmx.l.google.com2018-11-16 → 2018-11-16 · 4 obs

○ 2016-02-10 07:28:58
● 2018-11-16 20:31:38
○ 2026-02-27 16:10:50
○ 2026-05-09 10:37:22

○MXaspmx.l.google.com2018-11-16 → 2018-11-16 · 4 obs

○ 2016-02-10 07:28:58
● 2018-11-16 20:31:38
○ 2026-02-27 16:10:50
○ 2026-05-09 10:37:22

○MXmail.b-io.co2015-06-14 → 2015-06-14 · 3 obs

● 2015-06-14 01:37:48
○ 2015-11-19 14:07:04
○ 2026-05-09 10:37:22

○MXmailstore1.secureserver.net2015-11-19 → 2015-11-19 · 4 obs

○ 2015-06-14 01:37:48
● 2015-11-19 14:07:04
○ 2016-02-10 07:28:58
○ 2026-05-09 10:37:22

○MXsmtp.secureserver.net2015-11-19 → 2015-11-19 · 4 obs

○ 2015-06-14 01:37:48
● 2015-11-19 14:07:04
○ 2016-02-10 07:28:58
○ 2026-05-09 10:37:22

○A104.27.150.2202018-11-16 → 2018-11-16 · 4 obs

○ 2016-02-10 07:28:58
● 2018-11-16 20:31:38
○ 2026-02-27 16:10:50
○ 2026-05-09 10:37:22

○A104.27.151.2202018-11-16 → 2018-11-16 · 4 obs

○ 2016-02-10 07:28:58
● 2018-11-16 20:31:38
○ 2026-02-27 16:10:50
○ 2026-05-09 10:37:22

○A209.15.13.1342015-06-14 → 2015-06-14 · 3 obs

● 2015-06-14 01:37:48
○ 2015-11-19 14:07:04
○ 2026-05-09 10:37:22

○A2606:4700:30::681b:96dc2018-11-16 → 2018-11-16 · 4 obs

○ 2016-02-10 07:28:58
● 2018-11-16 20:31:38
○ 2026-02-27 16:10:50
○ 2026-05-09 10:37:22

○A2606:4700:30::681b:97dc2018-11-16 → 2018-11-16 · 4 obs

○ 2016-02-10 07:28:58
● 2018-11-16 20:31:38
○ 2026-02-27 16:10:50
○ 2026-05-09 10:37:22

●A3.33.224.1472026-02-27 → 2026-05-09 · 3 obs

○ 2018-11-16 20:31:38
● 2026-02-27 16:10:50
● 2026-05-09 10:37:22

○A50.63.202.572015-11-19 → 2015-11-19 · 4 obs

○ 2015-06-14 01:37:48
● 2015-11-19 14:07:04
○ 2016-02-10 07:28:58
○ 2026-05-09 10:37:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, a.gtld-servers.net, e.gtld-servers.net, b.gtld-servers.net...	-
wasabiginger.com	ns1.aftermarket.com, ns2.aftermarket.com	2 records

✅ Authoritative Response

Server:3.15.73.134

NS records: ns1.aftermarket.com, ns2.aftermarket.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for wasabiginger.com (unsigned zone)

⏱️ Timing

Total: 411ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.33.224.147`
NS	2	`ns2.aftermarket.com, ns1.aftermarket.com`
TXT	2	`afternic-verification-JMjLoGwNMDdPQhcrfw, f3af70b58684e0327b1544d7df12105d97e51ed6`
SOA	1	`ns1.aftermarket.com support.aftermarket.`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.aftermarket.com, ns2.aftermarket.com)

Analysis

IP Addresses

wasabiginger.com points to a single IP: 3.33.224.147.

Other host names, for instance j-a.com, spadom.com, modul8.co.uk, teldial.co and underdown.co.uk share IP numbers with wasabiginger.com.

Name Servers

Two name servers ns1.aftermarket.com and ns2.aftermarket.com handle delegation for wasabiginger.com.

wasabiginger.com uses the same name server setup as other domains, for example denverlens.com, i-adjust.com, klaw.co.uk, lockbuster.co.uk and slunicko.com.

wasabiginger.com partially shares name servers with other domains; examples include ecoit.co.uk, myco.be, sal.ae, littoral.be and yellowribbon.co.uk.

These name servers commonly accompany ns1.domain.io, ns2.domain.io, ns1.afternic.com and ns2.afternic.com.

Host names with two IP numbers:

ns1.aftermarket.com points to: 2600:1f16:529:db01::53 and 3.141.121.8

ns2.aftermarket.com points to: 2600:1f16:529:db00::53 and 3.15.73.134

wasabiginger.com - robtex.com