twinsensor.com - dns.ninja
twinsensor.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2a02:21d0::65:1:176🇧🇪 MAEHDROS-AS2a02:21d0::/32 Maehdros Hosting | ||||||
| PTR | ns2.maehdros.be | ||||||
| A | 188.65.217.176🇧🇪 MAEHDROS-AS188.65.216.0/21 Maehdros-NET | ||||||
| NS | dns12.ovh.net ⭐ | ||||||
| A | 2001:41d0:d00:f100::2🇫🇷 OVH2001:41d0::/32 IPv6 | ||||||
| PTR | dns12.ovh.net | ||||||
| A | 5.135.86.81🇫🇷 OVH5.135.0.0/16 | ||||||
| PTR | dns12.ovh.net | ||||||
| NS | ns12.ovh.net | ||||||
| A | 2001:41d0:b00:eb00::2🇫🇷 OVH2001:41d0::/32 IPv6 | ||||||
| PTR | ns12.ovh.net | ||||||
| A | 5.39.102.21🇫🇷 OVH5.39.0.0/17 ISP Paris, France | ||||||
| PTR | ns12.ovh.net | ||||||
| SOA | dns12.ovh.nettech@ovh.net 2021-02-03 #0 | ||||||
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=1782380460 | ||||||
Same first word
twinsensor.com |
DNS History
12 records (4 active, 8 former)
○NSdns1.name-services.com2016-07-08 → 2016-07-08 · 3 obs
○ 2017-03-14 04:40:38
○ 2026-06-25 09:42:54
●NSdns12.ovh.net2026-02-15 → 2026-06-25 · 3 obs
● 2026-02-15 22:25:12
● 2026-06-25 09:42:54
○NSdns2.name-services.com2016-07-08 → 2016-07-08 · 3 obs
○ 2017-03-14 04:40:38
○ 2026-06-25 09:42:54
○NSdns3.name-services.com2016-07-08 → 2016-07-08 · 3 obs
○ 2017-03-14 04:40:38
○ 2026-06-25 09:42:54
○NSdns4.name-services.com2016-07-08 → 2016-07-08 · 3 obs
○ 2017-03-14 04:40:38
○ 2026-06-25 09:42:54
○NSdns5.name-services.com2016-07-08 → 2016-07-08 · 3 obs
○ 2017-03-14 04:40:38
○ 2026-06-25 09:42:54
○NSns1.maehdros.be2017-03-14 → 2018-10-16 · 5 obs
● 2017-03-14 04:40:38
● 2018-10-16 11:04:44
○ 2026-02-15 22:25:12
○ 2026-06-25 09:42:54
●NSns12.ovh.net2026-02-15 → 2026-06-25 · 3 obs
● 2026-02-15 22:25:12
● 2026-06-25 09:42:54
○NSns2.maehdros.be2017-03-14 → 2018-10-16 · 5 obs
● 2017-03-14 04:40:38
● 2018-10-16 11:04:44
○ 2026-02-15 22:25:12
○ 2026-06-25 09:42:54
●A188.65.217.1762017-03-14 → 2026-06-25 · 3 obs
● 2017-03-14 04:40:38
● 2026-06-25 09:42:54
●A2a02:21d0::65:1:1762017-03-14 → 2026-06-25 · 3 obs
● 2017-03-14 04:40:38
● 2026-06-25 09:42:54
○A98.124.204.162016-07-08 → 2016-07-08 · 3 obs
○ 2017-03-14 04:40:38
○ 2026-06-25 09:42:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, l.gtld-servers.net, g.gtld-servers.net, d.gtld-servers.net... | - |
| twinsensor.com | dns12.ovh.net, ns12.ovh.net | - |
✅ Authoritative Response
Server:5.39.102.21
NS records: dns12.ovh.net, ns12.ovh.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for twinsensor.com (unsigned zone)
⏱️ Timing
Total: 2200ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 188.65.217.176 |
| AAAA | 1 | 2a02:21d0::65:1:176 |
| NS | 2 | dns12.ovh.net, ns12.ovh.net |
| SOA | 1 | dns12.ovh.net tech.ovh.net |
Analysis
IP Addresses
twinsensor.com points to the IP addresses 188.65.217.176 and 2a02:21d0::65:1:176
elioqual.info, clusters.be, aquawal.be plus two other host names have IP numbers in common with twinsensor.com.
Name Servers
twinsensor.com is served by two delegated name servers, dns12.ovh.net and ns12.ovh.net.
The name server configuration of twinsensor.com is shared with other domains, for instance emoticones.com, domobroc.com, motofun.be and two others.
At least some of twinsensor.com's name servers are shared with other domains, for example jadenthompson.com and mcdalloz.fr.
Each of the two host names carries two IP addresses: dns12.ovh.net points to 5.135.86.81 and 2001:41d0:d00:f100::2, and ns12.ovh.net points to 5.39.102.21 and 2001:41d0:b00:eb00::2.