interdomus.com - dns.ninja
interdomus.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.domainrecover.com ⚠️ Not in zone NS records | ||||||
| A | 149.248.38.58🇺🇸 AS-VULTR149.248.32.0/20 Vultr Assigned Prefix | ||||||
| PTR | 149.248.38.58.vultrusercontent.com | ||||||
| NS | ns2.domainrecover.com ⚠️ Not in zone NS records | ||||||
| A | 199.247.16.62🇩🇪 AS-VULTR199.247.16.0/21 Vultr Assigned Prefix | ||||||
| PTR | 199.247.16.62.vultrusercontent.com | ||||||
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=1782558390 | ||||||
Same first word
interdomus.pl |
interdomus.com |
interdomus.de |
Similar names
drumsonite.com |
intermodus.de |
mediturnos.com |
mountrides.com |
termisound.com |
remitsound.nl |
trimendous.net |
dounritmes.nl |
routeminds.com |
DNS History
13 records (2 active, 11 former)
○NShost.tradenames.com2015-10-24 → 2016-04-02 · 4 obs
● 2016-04-02 08:36:46
○ 2016-09-22 10:13:52
○ 2026-06-27 11:34:46
○NSns.tradenames.com2015-10-24 → 2016-04-02 · 4 obs
● 2016-04-02 08:36:46
○ 2016-09-22 10:13:52
○ 2026-06-27 11:34:46
●NSns1.domainrecover.com2026-02-18 → 2026-06-27 · 3 obs
● 2026-02-18 16:29:26
● 2026-06-27 11:34:46
○NSns1.dsredirection.com2016-09-22 → 2016-09-22 · 4 obs
● 2016-09-22 10:13:52
○ 2017-06-11 13:00:28
○ 2026-06-27 11:34:46
●NSns2.domainrecover.com2026-02-18 → 2026-06-27 · 3 obs
● 2026-02-18 16:29:26
● 2026-06-27 11:34:46
○NSns2.dsredirection.com2016-09-22 → 2016-09-22 · 4 obs
● 2016-09-22 10:13:52
○ 2017-06-11 13:00:28
○ 2026-06-27 11:34:46
○MXmxs1.tradenames.com2015-05-28 → 2016-04-02 · 4 obs
● 2016-04-02 08:36:46
○ 2016-09-22 10:13:52
○ 2026-06-27 11:34:46
○MXmxs2.tradenames.com2015-05-28 → 2016-04-02 · 4 obs
● 2016-04-02 08:36:46
○ 2016-09-22 10:13:52
○ 2026-06-27 11:34:46
○A141.8.230.202016-09-22 → 2016-09-22 · 4 obs
● 2016-09-22 10:13:52
○ 2017-06-11 13:00:28
○ 2026-06-27 11:34:46
○A66.45.246.1402015-10-24 → 2016-04-02 · 5 obs
● 2015-10-24 19:25:54
● 2016-04-02 08:36:46
○ 2016-09-22 10:13:52
○ 2026-06-27 11:34:46
○A67.209.228.1072015-05-28 → 2015-05-28 · 3 obs
○ 2015-10-24 19:25:54
○ 2026-06-27 11:34:46
○CNAMEpres.serverhome.com2016-09-22 → 2017-06-11 · 4 obs
● 2017-06-11 13:00:28
○ 2026-02-18 16:29:26
○ 2026-06-27 11:34:46
○CNAMEthie5ku9.dsgeneration.com2016-09-22 → 2016-09-22 · 3 obs
○ 2017-06-11 13:00:28
○ 2026-06-27 11:34:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net... | - |
| interdomus.com | ns1.domainrecover.com, ns2.domainrecover.com | 2 records |
✅ Authoritative Response
Server:199.247.16.62
NS records: ns1.domainrecover.com, ns2.domainrecover.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for interdomus.com (unsigned zone)
⏱️ Timing
Total: 228ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.domainrecover.com, ns2.domainrecover.com)
Analysis
Name Servers
interdomus.com is delegated to two name servers: ns1.domainrecover.com and ns2.domainrecover.com.
The name server configuration of interdomus.com is shared with other domains, for instance in-search.com, forex-forum.com, accole.com and two others.
interdomus.com partially shares its NS delegation with several other domains, including j4you.com, e-idcard.com, energimedia.com and two others.
The name servers ns1.serverhome.com, ns2.serverhome.com, ns2.servering.com and ns.servering.com are often found in use alongside these name servers.
ns1.domainrecover.com resolves to 149.248.38.58. ns2.domainrecover.com resolves to 199.247.16.62. Both host names point to a single IP number.