server3.digirize.com - dns.ninja
server3.digirize.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 198.50.241.84🇨🇦 OVH198.50.128.0/17 Hosting route | ||||||
| PTR | server3.digirize.com | ||||||
digirize.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 149.56.26.66🇨🇦 OVH149.56.0.0/16 Hosting route | ||||||
| NS | iris.ns.cloudflare.com ⭐ | ||||||
| NS | kip.ns.cloudflare.com | ||||||
| MX | digirize.com ⭐ | ||||||
| TXT | v=spf1 ip4:149.56.26.66 +a +mx +ip4:167.114.52.209 ~all | ||||||
| TXT | v=spf1 ip4:149.56.26.66 +a +mx +ip4:198.50.241.84 +ip4:198.50.241.84 ~all | ||||||
| SOA | iris.ns.cloudflare.comdns@cloudflare.com serial=2408516471 | ||||||
PTR for
Same first word
server3.ru |
server3.com |
server3.tk |
server3.bplaced.net |
server3.org |
server3.cloud |
server3.nagoya |
server3.space |
server3.net |
server3.eu |
server3.eu.com |
server3.co.uk |
server3.nl |
server3.cc |
server3.se |
server3.info |
Similar names
DNS History
2 records (1 active, 1 former)
○A149.56.20.2022017-05-12 → 2020-12-06 · 3 obs
● 2017-05-12 11:37:24
● 2020-12-06 03:18:42
○ 2026-08-10 21:11:02
● 2020-12-06 03:18:42
○ 2026-08-10 21:11:02
●A198.50.241.842026-08-10 → 2026-08-10 · 2 obs
○ 2020-12-06 03:18:42
● 2026-08-10 21:11:02
● 2026-08-10 21:11:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| digirize.com | kip.ns.cloudflare.com, iris.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.193.128
NS records: kip.ns.cloudflare.com, iris.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for digirize.com (unsigned zone)
⏱️ Timing
Total: 115ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 198.50.241.84 |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (kip.ns.cloudflare.com, kip.ns.cloudflare.com, kip.ns.cloudflare.com...)
Analysis
IP Addresses
server3.digirize.com resolves to one IP address: 198.50.241.84.