batchrequestforpayment.com - dns.ninja
batchrequestforpayment.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 146.190.33.190🇺🇸 DIGITALOCEAN146.190.32.0/19 DigitalOcean | ||||||
| NS | ns1.mydomain.com ⭐ | ||||||
| A | 172.64.52.99🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.mydomain.com | ||||||
| A | 172.64.53.76🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| MX | mx.batchrequestforpayment.com ⭐ | ||||||
| A | 146.190.33.190🇺🇸 DIGITALOCEAN146.190.32.0/19 DigitalOcean | ||||||
| TXT | v=spf1 ip4:66.96.128.0/18 include:websitewelcome.com ?all | ||||||
| SOA | NS1.MYDOMAIN.comnamehost@WORLDNIC.com serial=126072314 | ||||||
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.netnstld@verisign-grs.com serial=1791646879 | ||||||
Subdomains
mx.batchrequestforpayment.com |
Same first word
batchrequestforpayment.com |
Previous names
Next names
DNS History
4 records (4 active, 0 former)
●NSns1.mydomain.com2026-09-24 → 2026-10-10 · 2 obs
● 2026-10-10 16:07:08
●NSns2.mydomain.com2026-09-24 → 2026-10-10 · 2 obs
● 2026-10-10 16:07:08
●MXmx.batchrequestforpayment.com2026-09-24 → 2026-10-10 · 2 obs
● 2026-10-10 16:07:08
●A146.190.33.1902026-09-24 → 2026-10-10 · 2 obs
● 2026-10-10 16:07:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, d.gtld-servers.net, c.gtld-servers.net, l.gtld-servers.net... | - |
| batchrequestforpayment.com | ns1.mydomain.com, ns2.mydomain.com | 2 records |
✅ Authoritative Response
Server:172.64.52.99
NS records: ns1.mydomain.com, ns2.mydomain.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for batchrequestforpayment.com (unsigned zone)
⏱️ Timing
Total: 329ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 146.190.33.190 |
| NS | 2 | ns1.mydomain.com, ns2.mydomain.com |
| MX | 1 | mx.batchrequestforpayment.com (pri: 30) |
| TXT | 1 | v=spf1 ip4:66.96.128.0/18 include:websit |
| SOA | 1 | NS1.MYDOMAIN.com namehost.WORLDNIC.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.mydomain.com, ns2.mydomain.com)
Analysis
Hierarchy
mx.batchrequestforpayment.com is a subdomain of batchrequestforpayment.com.
IP Addresses
batchrequestforpayment.com resolves to just one IP address, 146.190.33.190.
Two other host names, along with signuprtp.com, createrfpfileformat.com and requestsforpayments.com, also share IP numbers with batchrequestforpayment.com.
Name Servers
Two name servers handle the delegation for batchrequestforpayment.com: ns1.mydomain.com and ns2.mydomain.com.
batchrequestforpayment.com shares its NS records with other domains, for example youactify.com, zanos.org, brisemorgen.com and two others.
The name servers of batchrequestforpayment.com overlap at least partially with those of other domains — among them yourfutureontheline.com, artistrybride.com, softmusic.net and two more.
These name servers commonly co-occur with the name servers ns3.mydomain.com, ns4.mydomain.com, ns1.yourhostingaccount.com and ns2.yourhostingaccount.com.
Both ns1.mydomain.com and ns2.mydomain.com have a single IP address each — ns1.mydomain.com resolves to 172.64.52.99 while ns2.mydomain.com resolves to 172.64.53.76.
Mail Servers
The sole mail server for batchrequestforpayment.com is mx.batchrequestforpayment.com.
mx.batchrequestforpayment.com carries a single IP number, which is 146.190.33.190.