paywelly.com - robtex.com

paywelly.com

DNSSEC⚠️ Not signed
A216.150.1.1🇨🇦 Amazon216.150.1.0/24 EC2 Prefix
A216.150.1.193🇨🇦 Amazon216.150.1.0/24 EC2 Prefix
NSns1.vercel-dns.com ⭐
A2620:4d:4000:6259:7:13:0:1🇺🇸 NSONE2620:4d:4000::/48 2620:4D:4000::/48
PTRdns1.p13.nsone.net
A198.51.44.13🇺🇸 NSONE198.51.44.0/24 198.51.44.0
PTRdns1.p13.nsone.net
NSns2.vercel-dns.com
A2a00:edc0:6259:7:13::2🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2
PTRdns2.p13.nsone.net
A198.51.45.13🇺🇸 NSONE198.51.45.0/24 198.51.45.0
PTRdns2.p13.nsone.net
MXaspmx.l.google.com ⭐
A2607:f8b0:4004:c21::1b🇺🇸 Google2607:f8b0:4004::/48
PTRpe-in-f27.1e100.net
A142.250.31.27🇺🇸 Google142.250.31.0/24
PTRbj-in-f27.1e100.net
MXalt1.aspmx.l.google.com(5)
A2800:3f0:4003:c0f::1a🇨🇱 Google2800:3f0:4003::/48
A108.177.123.26🇺🇸 Google108.177.123.0/24
PTRlcscld-in-f26.1e100.net
MXalt2.aspmx.l.google.com(5)
A2a00:1450:400b:c02::1b🇮🇪 Google2a00:1450:400b::/48
PTRdj-in-f27.1e100.net
A172.253.116.27🇺🇸 Google172.253.116.0/24
PTRdj-in-f27.1e100.net
MXalt3.aspmx.l.google.com(10)
A2a00:1450:4009:c0f::1a🇬🇧 Google2a00:1450:4009::/48
PTRyulhrs-in-f26.1e100.net
A192.178.223.27🇺🇸 Google192.178.223.0/24
PTRyulhrs-in-f27.1e100.net
MXalt4.aspmx.l.google.com(10)
A2a00:1450:400c:c23::1a🇧🇪 Google2a00:1450:400c::/48
PTRyubrupd-in-f26.1e100.net
A172.253.157.26🇺🇸 Google172.253.0.0/16
PTRyubrupd-in-f26.1e100.net
SOAns1.vercel-dns.comhostmaster@nsone.net serial=1778874440

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1784173747

Same first word

paywelly.com

DNS History

17 records (9 active, 8 former)

2020202120222023202420252026NSns1.vercel-dns.comns2.vercel-dns.comdns1.registrar-servers.comdns2.registrar-servers.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comeforward1.registrar-servers.comeforward2.registrar-servers.comeforward3.registrar-servers.comeforward4.registrar-servers.comeforward5.registrar-servers.comA216.150.1.1216.150.1.193216.150.16.193
○NSdns1.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs
● 2019-12-15 20:21:56
○ 2026-07-07 09:25:36
○ 2026-07-16 04:04:32
○NSdns2.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs
● 2019-12-15 20:21:56
○ 2026-07-07 09:25:36
○ 2026-07-16 04:04:32
●NSns1.vercel-dns.com2026-07-07 → 2026-07-16 · 3 obs
○ 2019-12-15 20:21:56
● 2026-07-07 09:25:36
● 2026-07-16 04:04:32
●NSns2.vercel-dns.com2026-07-07 → 2026-07-16 · 3 obs
○ 2019-12-15 20:21:56
● 2026-07-07 09:25:36
● 2026-07-16 04:04:32
●MXalt1.aspmx.l.google.com2026-07-07 → 2026-07-16 · 3 obs
○ 2019-12-15 20:21:56
● 2026-07-07 09:25:36
● 2026-07-16 04:04:32
●MXalt2.aspmx.l.google.com2026-07-07 → 2026-07-16 · 3 obs
○ 2019-12-15 20:21:56
● 2026-07-07 09:25:36
● 2026-07-16 04:04:32
●MXalt3.aspmx.l.google.com2026-07-07 → 2026-07-16 · 3 obs
○ 2019-12-15 20:21:56
● 2026-07-07 09:25:36
● 2026-07-16 04:04:32
●MXalt4.aspmx.l.google.com2026-07-07 → 2026-07-16 · 3 obs
○ 2019-12-15 20:21:56
● 2026-07-07 09:25:36
● 2026-07-16 04:04:32
●MXaspmx.l.google.com2026-07-07 → 2026-07-16 · 3 obs
○ 2019-12-15 20:21:56
● 2026-07-07 09:25:36
● 2026-07-16 04:04:32
○MXeforward1.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs
● 2019-12-15 20:21:56
○ 2026-07-07 09:25:36
○ 2026-07-16 04:04:32
○MXeforward2.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs
● 2019-12-15 20:21:56
○ 2026-07-07 09:25:36
○ 2026-07-16 04:04:32
○MXeforward3.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs
● 2019-12-15 20:21:56
○ 2026-07-07 09:25:36
○ 2026-07-16 04:04:32
○MXeforward4.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs
● 2019-12-15 20:21:56
○ 2026-07-07 09:25:36
○ 2026-07-16 04:04:32
○MXeforward5.registrar-servers.com2019-12-15 → 2019-12-15 · 3 obs
● 2019-12-15 20:21:56
○ 2026-07-07 09:25:36
○ 2026-07-16 04:04:32
●A216.150.1.12026-07-16 → 2026-07-16 · 2 obs
○ 2026-07-07 09:25:36
● 2026-07-16 04:04:32
●A216.150.1.1932026-07-07 → 2026-07-16 · 2 obs
● 2026-07-07 09:25:36
● 2026-07-16 04:04:32
○A216.150.16.1932026-07-07 → 2026-07-07 · 2 obs
● 2026-07-07 09:25:36
○ 2026-07-16 04:04:32

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comf.gtld-servers.net, d.gtld-servers.net, j.gtld-servers.net, a.gtld-servers.net...-
paywelly.comns1.vercel-dns.com, ns2.vercel-dns.com4 records

✅ Authoritative Response

Server:198.51.45.13

NS records: ns1.vercel-dns.com, ns2.vercel-dns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for paywelly.com (unsigned zone)

⏱️ Timing

Total: 222ms | Queries: -

📄 Records

TypeCountSample Data
A2216.150.1.65, 216.150.16.129
NS2ns1.vercel-dns.com, ns2.vercel-dns.com
MX5aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...
SOA1ns1.vercel-dns.com hostmaster.nsone.net

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.vercel-dns.com, ns1.vercel-dns.com, ns2.vercel-dns.com...)

Analysis

IP Addresses

paywelly.com directs to two IP numbers, 216.150.1.1 and 216.150.1.193

Among the host names that share IP numbers with paywelly.com are khupo.org, creditinsurancequestionnaire.com, afrosynergy.com and two others.

Name Servers

paywelly.com has two authoritative name servers — ns1.vercel-dns.com and ns2.vercel-dns.com.

paywelly.com has the same name server delegation as a number of other domains, such as emiliobogantes.com, marijuanaonbase.com, dreamsofdarkness.com and two more.

Some of paywelly.com's name servers are also used by other domains, including lxxyx.cn, organiz.org, relink.ro and georgesduverger.com.

Both ns1.vercel-dns.com and ns2.vercel-dns.com have two IP addresses each. ns1.vercel-dns.com resolves to 198.51.44.13 and 2620:4d:4000:6259:7:13:0:1; ns2.vercel-dns.com resolves to 198.51.45.13 and 2a00:edc0:6259:7:13::2.

Mail Servers

Mail for paywelly.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

paywelly.com shares at least some of its mail servers with other domains — for example inhogagroup.com, hf3construction.com, ns500698.ns500758.ns500758.ns500758.ns500758.ns500698.ns500698.ns500698.ns500736.ns500698.ns500698.ns500708.ns500686.ns500652.ns500576.trackreceptor.com and two more.

It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.

Hosts with two IP numbers each:

aspmx.l.google.com resolves to 142.250.31.27 and 2607:f8b0:4004:c21::1b.

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

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

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

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