`sovapay.com`

DNSSEC	⚠️ Not signed
A	3.33.130.190^{🇺🇸 Amazon3.33.128.0/20}
A	15.197.148.33^{🇺🇸 Amazon15.197.144.0/20}
NS	`ns45.domaincontrol.com` ⭐
		A	2603:5:2162::17^{🇺🇸 GODADDY-DNS2603:5:2160::/44}
			PTR	`ns45.domaincontrol.com`
		A	97.74.102.23^{🇺🇸 GODADDY-DNS97.74.102.0/23}
NS	`ns46.domaincontrol.com`
		A	2603:5:2262::17^{🇺🇸 GODADDY-DNS2603:5:2260::/44}
			PTR	`ns46.domaincontrol.com`
		A	173.201.70.23^{🇺🇸 GODADDY-DNS173.201.70.0/23}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c06::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bg-in-f27.1e100.net`
		A	142.251.163.27^{🇺🇸 Google142.251.163.0/24}
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
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}
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
TXT	`google-site-verification=wuMN4co3KK3nyZ01Ru5HWwHzjYKbfjiDcg-rsIRCO2g`
TXT	`v=spf1 include:dc-aa8e722993._spfm.sovapay.com ~all`
SOA	`ns45.domaincontrol.com`dns@jomax.net 2024-03-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=1784610432

Same first word

sovapay.com

DNS History

17 records (9 active, 8 former)

○NSdns1.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 04:14:54
○ 2026-03-29 13:52:32
○ 2026-07-21 05:35:00

○NSdns2.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 04:14:54
○ 2026-03-29 13:52:32
○ 2026-07-21 05:35:00

●NSns45.domaincontrol.com2026-03-29 → 2026-07-21 · 3 obs

○ 2019-12-15 04:14:54
● 2026-03-29 13:52:32
● 2026-07-21 05:35:00

●NSns46.domaincontrol.com2026-03-29 → 2026-07-21 · 3 obs

○ 2019-12-15 04:14:54
● 2026-03-29 13:52:32
● 2026-07-21 05:35:00

●MXalt1.aspmx.l.google.com2026-03-29 → 2026-07-21 · 3 obs

○ 2019-12-15 04:14:54
● 2026-03-29 13:52:32
● 2026-07-21 05:35:00

●MXalt2.aspmx.l.google.com2026-03-29 → 2026-07-21 · 3 obs

○ 2019-12-15 04:14:54
● 2026-03-29 13:52:32
● 2026-07-21 05:35:00

●MXalt3.aspmx.l.google.com2026-03-29 → 2026-07-21 · 3 obs

○ 2019-12-15 04:14:54
● 2026-03-29 13:52:32
● 2026-07-21 05:35:00

●MXalt4.aspmx.l.google.com2026-03-29 → 2026-07-21 · 3 obs

○ 2019-12-15 04:14:54
● 2026-03-29 13:52:32
● 2026-07-21 05:35:00

●MXaspmx.l.google.com2026-03-29 → 2026-07-21 · 3 obs

○ 2019-12-15 04:14:54
● 2026-03-29 13:52:32
● 2026-07-21 05:35:00

○MXeforward1.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 04:14:54
○ 2026-03-29 13:52:32
○ 2026-07-21 05:35:00

○MXeforward2.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 04:14:54
○ 2026-03-29 13:52:32
○ 2026-07-21 05:35:00

○MXeforward3.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 04:14:54
○ 2026-03-29 13:52:32
○ 2026-07-21 05:35:00

○MXeforward4.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 04:14:54
○ 2026-03-29 13:52:32
○ 2026-07-21 05:35:00

○MXeforward5.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 04:14:54
○ 2026-03-29 13:52:32
○ 2026-07-21 05:35:00

●A15.197.148.332026-03-29 → 2026-07-21 · 3 obs

○ 2019-12-15 04:14:54
● 2026-03-29 13:52:32
● 2026-07-21 05:35:00

○A192.64.119.102019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 04:14:54
○ 2026-03-29 13:52:32
○ 2026-07-21 05:35:00

●A3.33.130.1902026-03-29 → 2026-07-21 · 3 obs

○ 2019-12-15 04:14:54
● 2026-03-29 13:52:32
● 2026-07-21 05:35:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, e.gtld-servers.net, i.gtld-servers.net, m.gtld-servers.net...	-
sovapay.com	ns45.domaincontrol.com, ns46.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.102.23

NS records: ns45.domaincontrol.com, ns46.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sovapay.com (unsigned zone)

⏱️ Timing

Total: 472ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`3.33.130.190, 15.197.148.33`
NS	2	`ns45.domaincontrol.com, ns46.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	2	`google-site-verification=wuMN4co3KK3nyZ0, v=spf1 include:dc-aa8e722993._spfm.sovap`
SOA	1	`ns45.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns45.domaincontrol.com, ns45.domaincontrol.com, ns46.domaincontrol.com...)

Analysis

IP Addresses

sovapay.com has two IP addresses: 3.33.130.190 and 15.197.148.33

phowitt.com, symphonybysyra.com, bluephoenixvape.com and two other host names share IP numbers with sovapay.com.

Name Servers

Two name servers handle the delegation for sovapay.com: ns45.domaincontrol.com and ns46.domaincontrol.com.

sovapay.com uses the same name servers as several other domains — among them brokr.co, vehiclesunique.net, whynothope.com and two more.

ns45.domaincontrol.com and ns46.domaincontrol.com both carry two IP addresses. The A records for ns45.domaincontrol.com are 97.74.102.23 and 2603:5:2162::17; the A records for ns46.domaincontrol.com are 173.201.70.23 and 2603:5:2262::17.

Mail Servers

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

sovapay.com has at least partial mail server overlap with other domains such as awakelabs.com, interactive-pages.com, kemya-b.com and two more.

These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 4 others.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com resolves to two addresses: 142.251.163.27 and 2607:f8b0:4004:c06::1b.

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

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.26 and 2a00:1450:4009:c0f::1b.

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