relationship-api.bdreporting.com - dns.ninja
relationship-api.bdreporting.com
| CNAME | ingress.bdreporting.com | ||||||
| DNSSEC | ⚠️ Not signed | ||||||
| A | 199.36.128.240🇺🇸 AS13938199.36.128.0/22 | ||||||
bdreporting.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 199.36.128.195🇺🇸 AS13938199.36.128.0/22 | ||||||
| NS | inetdns.ssnc.cloud ⭐ | ||||||
| NS | inetdns1.ssnc.cloud | ||||||
| TXT | MS=ms68075693 | ||||||
| TXT | _mv3ayu7f4az5szcaqgyzl25k8z0q227 | ||||||
| TXT | google-site-verification=cwq21xnfszk-hmrjutwe-ddl3kf11tfyyiqxdhtw8ay | ||||||
| TXT | google-site-verification=e5A4-UeZdOlmy2xoY2E7o3QDP51Xwp05e4vs1S4Y9ac | ||||||
| TXT | v=spf1 ip4:209.34.243.112/28 ip4:72.15.234.192/27 ip4:199.36.128.0/22 include... | ||||||
| SOA | inetdns1.ssnc.clouddns@cloudflare.com serial=2410629104 | ||||||
rank #156932 in the tld
📈 Tranco rank: #176,375
DNS History
2 records (1 active, 1 former)
○A199.36.128.2472019-12-20 → 2019-12-20 · 2 obs
● 2019-12-20 05:34:22
○ 2026-07-28 05:17:52
○ 2026-07-28 05:17:52
●CNAMEingress.bdreporting.com2026-07-28 → 2026-07-28 · 1 obs
● 2026-07-28 05:17:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| bdreporting.com | inetdns.ssnc.cloud, inetdns1.ssnc.cloud | - |
✅ Authoritative Response
Server:198.41.223.237
NS records: inetdns.ssnc.cloud, inetdns1.ssnc.cloud
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bdreporting.com (unsigned zone)
⏱️ Timing
Total: 241ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| CNAME | 1 | ingress.bdreporting.com |
Analysis
IP Addresses
relationship-api.bdreporting.com resolves to just one IP address, 199.36.128.240.
Other host names share IP numbers with relationship-api.bdreporting.com; ingress.bdreporting.com is one such example.