requestforpaymentapi.com - dns.ninja
requestforpaymentapi.com
| 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.requestforpaymentapi.com ⭐ | ||||||
| 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=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=1792922026 | ||||||
Same first word
requestforpaymentapi.com |
Similar names
Previous names
Next names
DNS History
4 records (4 active, 0 former)
●NSns1.mydomain.com2026-09-25 → 2026-10-25 · 2 obs
● 2026-10-25 10:00:08
●NSns2.mydomain.com2026-09-25 → 2026-10-25 · 2 obs
● 2026-10-25 10:00:08
●MXmx.requestforpaymentapi.com2026-09-25 → 2026-10-25 · 2 obs
● 2026-10-25 10:00:08
●A146.190.33.1902026-09-25 → 2026-10-25 · 2 obs
● 2026-10-25 10:00:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net, b.gtld-servers.net... | - |
| requestforpaymentapi.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 requestforpaymentapi.com (unsigned zone)
⏱️ Timing
Total: 472ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 146.190.33.190 |
| NS | 2 | ns1.mydomain.com, ns2.mydomain.com |
| MX | 1 | mx.requestforpaymentapi.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
IP Addresses
requestforpaymentapi.com directs to one IP number, which is 146.190.33.190.
Among the host names that share IP numbers with requestforpaymentapi.com are importreal-timepaymentsfile.com, requestforpayments.com, real-timepaymentsimportfileformats.com and two others.
Name Servers
requestforpaymentapi.com has two authoritative name servers — ns1.mydomain.com and ns2.mydomain.com.
requestforpaymentapi.com has the same name server delegation as a number of other domains, such as forestfelines.org, jastar.ca, nexaforce.io and two more.
requestforpaymentapi.com has at least partial name server overlap with other domains, such as thirtyminutehit.com, usspeedtest.net, hologramz.net and two others.
It is common to find these name servers paired with the name servers ns3.mydomain.com, ns4.mydomain.com, ns1.yourhostingaccount.com and ns2.yourhostingaccount.com.
ns1.mydomain.com directs to 172.64.52.99 and ns2.mydomain.com directs to 172.64.53.76; each host name points to exactly one IP number.
Mail Servers
requestforpaymentapi.com routes its mail through a single mail server, mx.requestforpaymentapi.com.
mx.requestforpaymentapi.com points to one IP number — 146.190.33.190.