requestforpay.net - dns.ninja
requestforpay.net
| DNSSEC | ⚠️ Not signed | ||||||
| A | 146.190.33.190🇺🇸 DIGITALOCEAN146.190.32.0/19 DigitalOcean | ||||||
| PTR | 1479463.cloudwaysapps.com | ||||||
| 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.requestforpay.net ⭐ | ||||||
| A | 146.190.33.190🇺🇸 DIGITALOCEAN146.190.32.0/19 DigitalOcean | ||||||
| PTR | 1479463.cloudwaysapps.com | ||||||
| TXT | v=spf1 ip4:66.96.128.0/18 include:websitewelcome.com ?all | ||||||
| SOA | NS1.MYDOMAIN.COMnamehost@WORLDNIC.COM serial=125120317 | ||||||
net
| 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=1785482927 | ||||||
Subdomains
mx.requestforpay.net |
Same first word
requestforpay.net |
requestforpay.com |
DNS History
4 records (4 active, 0 former)
●NSns1.mydomain.com2026-06-25 → 2026-07-31 · 2 obs
● 2026-07-31 07:39:16
●NSns2.mydomain.com2026-06-25 → 2026-07-31 · 2 obs
● 2026-07-31 07:39:16
●MXmx.requestforpay.net2026-06-25 → 2026-07-31 · 2 obs
● 2026-07-31 07:39:16
●A146.190.33.1902026-06-25 → 2026-07-31 · 2 obs
● 2026-07-31 07:39:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | b.gtld-servers.net, a.gtld-servers.net, l.gtld-servers.net, j.gtld-servers.net... | - |
| requestforpay.net | ns1.mydomain.com, ns2.mydomain.com | - |
✅ Authoritative Response
Server:172.64.52.99
NS records: ns1.mydomain.com, ns2.mydomain.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for requestforpay.net (unsigned zone)
⏱️ Timing
Total: 1216ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 146.190.33.190 |
| NS | 2 | ns2.mydomain.com, ns1.mydomain.com |
| MX | 1 | mx.requestforpay.net (pri: 30) |
| TXT | 1 | v=spf1 ip4:66.96.128.0/18 include:websit |
| SOA | 1 | NS1.MYDOMAIN.COM namehost.WORLDNIC.COM |
Analysis
Hierarchy
mx.requestforpay.net is delegated beneath requestforpay.net.
IP Addresses
requestforpay.net directs to one IP number, which is 146.190.33.190.
Further host names like mx.requestforpay.net and real-timeservice.com overlap in IP numbers with requestforpay.net.
Name Servers
Two name servers handle the delegation for requestforpay.net: ns1.mydomain.com and ns2.mydomain.com.
requestforpay.net has the same name server delegation as a number of other domains, such as ahp.one, kpsinfosystems.com, acme.space and two more.
There is at least partial name server overlap between requestforpay.net and other domains — arcanaentertainment.com, cultivatedmusic.com, americancomputerservices.com and two more among them.
These name servers tend to appear in combination with the name servers ns3.mydomain.com, ns4.mydomain.com, ns1.yourhostingaccount.com and ns2.yourhostingaccount.com.
ns1.mydomain.com → 172.64.52.99 and ns2.mydomain.com → 172.64.53.76: one IP number per host name.
Mail Servers
requestforpay.net routes its mail through a single mail server, mx.requestforpay.net.
mx.requestforpay.net carries a single IP number, which is 146.190.33.190.