avidance.com - dns.ninja

`avidance.com`

DNSSEC	⚠️ Not signed
A	76.76.21.21^{🇺🇸 Amazon76.76.21.0/24 EC2 Prefix}
NS	`ns35.domaincontrol.com` ⭐
		A	2603:5:21b1::12^{🇺🇸 GODADDY-DNS2603:5:21b0::/44}
			PTR	`ns35.domaincontrol.com`
		A	97.74.107.18^{🇺🇸 GODADDY-DNS97.74.106.0/23}
			PTR	`ns35.domaincontrol.com`
NS	`ns36.domaincontrol.com`
		A	2603:5:22b1::12^{🇺🇸 GODADDY-DNS2603:5:22b0::/44}
			PTR	`ns36.domaincontrol.com`
		A	173.201.75.18^{🇺🇸 GODADDY-DNS173.201.74.0/23}
			PTR	`ns36.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c0b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bj-in-f26.1e100.net`
		A	172.253.139.26^{🇺🇸 Google172.253.139.0/24}
			PTR	`yuiadsk-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 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.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
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.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=QOkfYXHF0AqwN5EPeVLzkwqMZRSlomHFT_Bm2Bqh81A`
TXT	`v=spf1 include:dc-aa8e722993._spfm.avidance.com ~all`
SOA	`ns35.domaincontrol.com`dns@jomax.net 2025-08-14 #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=1783779512

Same first word

avidance.com

Similar names

DNS History

13 records (8 active, 5 former)

○NSns13.domaincontrol.com2015-08-11 → 2017-03-16 · 4 obs

● 2015-08-11 22:02:26
● 2017-03-16 20:49:20
○ 2020-01-06 07:17:24
○ 2026-07-11 14:48:00

○NSns14.domaincontrol.com2015-08-11 → 2017-03-16 · 4 obs

● 2015-08-11 22:02:26
● 2017-03-16 20:49:20
○ 2020-01-06 07:17:24
○ 2026-07-11 14:48:00

●NSns35.domaincontrol.com2026-04-11 → 2026-07-11 · 3 obs

○ 2020-01-06 07:17:24
● 2026-04-11 15:32:54
● 2026-07-11 14:48:00

●NSns36.domaincontrol.com2026-04-11 → 2026-07-11 · 3 obs

○ 2020-01-06 07:17:24
● 2026-04-11 15:32:54
● 2026-07-11 14:48:00

●MXalt1.aspmx.l.google.com2026-04-11 → 2026-07-11 · 3 obs

○ 2020-01-06 07:17:24
● 2026-04-11 15:32:54
● 2026-07-11 14:48:00

●MXalt2.aspmx.l.google.com2026-04-11 → 2026-07-11 · 3 obs

○ 2020-01-06 07:17:24
● 2026-04-11 15:32:54
● 2026-07-11 14:48:00

●MXalt3.aspmx.l.google.com2026-04-11 → 2026-07-11 · 3 obs

○ 2020-01-06 07:17:24
● 2026-04-11 15:32:54
● 2026-07-11 14:48:00

●MXalt4.aspmx.l.google.com2026-04-11 → 2026-07-11 · 3 obs

○ 2020-01-06 07:17:24
● 2026-04-11 15:32:54
● 2026-07-11 14:48:00

●MXaspmx.l.google.com2026-04-11 → 2026-07-11 · 3 obs

○ 2020-01-06 07:17:24
● 2026-04-11 15:32:54
● 2026-07-11 14:48:00

○MXmailstore1.secureserver.net2015-08-11 → 2017-03-16 · 4 obs

● 2015-08-11 22:02:26
● 2017-03-16 20:49:20
○ 2020-01-06 07:17:24
○ 2026-07-11 14:48:00

○MXsmtp.secureserver.net2015-08-11 → 2017-03-16 · 4 obs

● 2015-08-11 22:02:26
● 2017-03-16 20:49:20
○ 2020-01-06 07:17:24
○ 2026-07-11 14:48:00

○A50.63.202.422015-08-11 → 2017-03-16 · 4 obs

● 2015-08-11 22:02:26
● 2017-03-16 20:49:20
○ 2020-01-06 07:17:24
○ 2026-07-11 14:48:00

●A76.76.21.212026-04-11 → 2026-07-11 · 3 obs

○ 2020-01-06 07:17:24
● 2026-04-11 15:32:54
● 2026-07-11 14:48:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
avidance.com	ns35.domaincontrol.com, ns36.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.107.18

NS records: ns35.domaincontrol.com, ns36.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for avidance.com (unsigned zone)

⏱️ Timing

Total: 209ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`76.76.21.21`
NS	2	`ns35.domaincontrol.com, ns36.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	2	`google-site-verification=QOkfYXHF0AqwN5E, v=spf1 include:dc-aa8e722993._spfm.avida`
SOA	1	`ns35.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns35.domaincontrol.com, ns35.domaincontrol.com, ns36.domaincontrol.com...)

Analysis

IP Addresses

avidance.com has exactly one IP address — 76.76.21.21.

avvall.com, secure.spax.us, veri.co plus two other host names have IP numbers in common with avidance.com.

Name Servers

Two name servers handle the delegation for avidance.com: ns35.domaincontrol.com and ns36.domaincontrol.com.

The name server configuration of avidance.com is shared with other domains, for instance 4tb.de, sedonadog.com, popcurse.net and two others.

The name servers for avidance.com overlap at least in part with those of other domains, including corporatemedicalservices.com and sumnersherifftn.gov.

ns35.domaincontrol.com and ns36.domaincontrol.com both carry two IP addresses. The A records for ns35.domaincontrol.com are 97.74.107.18 and 2603:5:21b1::12; the A records for ns36.domaincontrol.com are 173.201.75.18 and 2603:5:22b1::12.

Mail Servers

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

At least some of the mail servers used by avidance.com are shared with other domains: jtia.jp, verdino.co, titan.com.pa and two others among them.

These mail servers are often deployed together with alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx.l.google.com resolves to two addresses: 172.253.139.26 and 2607:f8b0:4004:c0b::1a.

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

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

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

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