requestforpay.net - robtex.com
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=1785453217 | ||||||
Same first word
requestforpay.net |
requestforpay.com |
DNS History
4 records (4 active, 0 former)
●NSns1.mydomain.com2026-06-25 → 2026-07-30 · 2 obs
● 2026-07-30 23:33:06
●NSns2.mydomain.com2026-06-25 → 2026-07-30 · 2 obs
● 2026-07-30 23:33:06
●MXmx.requestforpay.net2026-06-25 → 2026-07-30 · 2 obs
● 2026-07-30 23:33:06
●A146.190.33.1902026-06-25 → 2026-07-30 · 2 obs
● 2026-07-30 23:33:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| requestforpay.net | ns1.mydomain.com, ns2.mydomain.com | - |
✅ Authoritative Response
Server:172.64.53.76
NS records: ns1.mydomain.com, ns2.mydomain.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for requestforpay.net (unsigned zone)
⏱️ Timing
Total: 263ms | 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
IP Addresses
requestforpay.net resolves to one IP address: 146.190.33.190.
Other host names share IP numbers with requestforpay.net; real-timeservice.com is one such example.
Name Servers
requestforpay.net is served by two delegated name servers, ns1.mydomain.com and ns2.mydomain.com.
requestforpay.net uses the same name servers as several other domains — among them ahp.one, kpsinfosystems.com, acme.space and two more.
requestforpay.net partially shares its NS delegation with several other domains, including arcanaentertainment.com, cultivatedmusic.com, americancomputerservices.com and two others.
The name servers ns3.mydomain.com, ns4.mydomain.com, ns1.yourhostingaccount.com and ns2.yourhostingaccount.com are often found in use alongside these name servers.
ns1.mydomain.com resolves to 172.64.52.99. ns2.mydomain.com resolves to 172.64.53.76. Both host names point to a single IP number.
Mail Servers
Mail for requestforpay.net is handled by a single mail server, mx.requestforpay.net.
There is one IP number for mx.requestforpay.net: 146.190.33.190.