sensorberg.de - robtex.com
sensorberg.de
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.8.178.132🇺🇸 Amazon52.8.0.0/16 EC2 SFO Prefix | ||||||
| PTR | ec2-52-8-178-132.us-west-1.compute.amazonaws.com | ||||||
| A | 184.169.135.34🇺🇸 Amazon184.169.128.0/17 EC2 SFO prefix | ||||||
| NS | ns1.open-telekom-cloud.com ⭐ | ||||||
| A | 80.158.48.19🇩🇪 AS687880.158.48.0/20 belongs to 80.158.32.0/19 | ||||||
| NS | ns2.open-telekom-cloud.com | ||||||
| A | 93.188.242.252🇩🇪 AS687893.188.242.0/24 belongs to 93.188.240.0/21 delegated by SCZN-AS to DTAG for OTC | ||||||
| PTR | ns2.open-telekom-cloud.com | ||||||
| SOA | ns1.open-telekom-cloud.cominfrastructure@sensorberg.com serial=1 | ||||||
de
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | f.nic.de ⭐ | ||||||
| NS | a.nic.de | ||||||
| NS | l.de.net ⚠️ Not in parent delegation | ||||||
| NS | n.de.net ⚠️ Not in parent delegation | ||||||
| NS | s.de.net ⚠️ Not in parent delegation | ||||||
| NS | z.nic.de | ||||||
| SOA | f.nic.dedns-operations@denic.de serial=1774584053 | ||||||
Same first word
sensorberg.de |
sensorberg.com |
Similar names
DNS History
19 records (4 active, 15 former)
○NSns1-04.azure-dns.com2017-03-20 → 2017-03-20 · 4 obs
○ 2016-07-21 06:07:18
● 2017-03-20 10:12:12
○ 2019-12-28 22:52:30
○ 2026-03-27 04:28:46
● 2017-03-20 10:12:12
○ 2019-12-28 22:52:30
○ 2026-03-27 04:28:46
○NSns1.domainoffensive.de2015-05-25 → 2016-07-21 · 4 obs
● 2015-05-25 13:57:48
● 2016-07-21 06:07:18
○ 2017-03-20 10:12:12
○ 2026-03-27 04:28:46
● 2016-07-21 06:07:18
○ 2017-03-20 10:12:12
○ 2026-03-27 04:28:46
●NSns1.open-telekom-cloud.com2019-12-28 → 2026-03-27 · 3 obs
○ 2017-03-20 10:12:12
● 2019-12-28 22:52:30
● 2026-03-27 04:28:46
● 2019-12-28 22:52:30
● 2026-03-27 04:28:46
○NSns2-04.azure-dns.net2017-03-20 → 2017-03-20 · 4 obs
○ 2016-07-21 06:07:18
● 2017-03-20 10:12:12
○ 2019-12-28 22:52:30
○ 2026-03-27 04:28:46
● 2017-03-20 10:12:12
○ 2019-12-28 22:52:30
○ 2026-03-27 04:28:46
○NSns2.domainoffensive.de2015-05-25 → 2016-07-21 · 4 obs
● 2015-05-25 13:57:48
● 2016-07-21 06:07:18
○ 2017-03-20 10:12:12
○ 2026-03-27 04:28:46
● 2016-07-21 06:07:18
○ 2017-03-20 10:12:12
○ 2026-03-27 04:28:46
●NSns2.open-telekom-cloud.com2019-12-28 → 2026-03-27 · 3 obs
○ 2017-03-20 10:12:12
● 2019-12-28 22:52:30
● 2026-03-27 04:28:46
● 2019-12-28 22:52:30
● 2026-03-27 04:28:46
○NSns3-04.azure-dns.org2017-03-20 → 2017-03-20 · 4 obs
○ 2016-07-21 06:07:18
● 2017-03-20 10:12:12
○ 2019-12-28 22:52:30
○ 2026-03-27 04:28:46
● 2017-03-20 10:12:12
○ 2019-12-28 22:52:30
○ 2026-03-27 04:28:46
○NSns3.domainoffensive.de2015-10-19 → 2016-07-21 · 5 obs
○ 2015-05-25 13:57:48
● 2015-10-19 22:26:30
● 2016-07-21 06:07:18
○ 2017-03-20 10:12:12
○ 2026-03-27 04:28:46
● 2015-10-19 22:26:30
● 2016-07-21 06:07:18
○ 2017-03-20 10:12:12
○ 2026-03-27 04:28:46
○NSns4-04.azure-dns.info2017-03-20 → 2017-03-20 · 4 obs
○ 2016-07-21 06:07:18
● 2017-03-20 10:12:12
○ 2019-12-28 22:52:30
○ 2026-03-27 04:28:46
● 2017-03-20 10:12:12
○ 2019-12-28 22:52:30
○ 2026-03-27 04:28:46
○MXalt1.aspmx.l.google.com2015-05-25 → 2026-02-15 · 3 obs
● 2015-05-25 13:57:48
● 2026-02-15 22:45:18
○ 2026-03-27 04:28:46
● 2026-02-15 22:45:18
○ 2026-03-27 04:28:46
○MXalt2.aspmx.l.google.com2015-05-25 → 2026-02-15 · 3 obs
● 2015-05-25 13:57:48
● 2026-02-15 22:45:18
○ 2026-03-27 04:28:46
● 2026-02-15 22:45:18
○ 2026-03-27 04:28:46
○MXaspmx.l.google.com2015-05-25 → 2026-02-15 · 3 obs
● 2015-05-25 13:57:48
● 2026-02-15 22:45:18
○ 2026-03-27 04:28:46
● 2026-02-15 22:45:18
○ 2026-03-27 04:28:46
○MXaspmx2.googlemail.com2015-05-25 → 2026-02-15 · 3 obs
● 2015-05-25 13:57:48
● 2026-02-15 22:45:18
○ 2026-03-27 04:28:46
● 2026-02-15 22:45:18
○ 2026-03-27 04:28:46
○MXaspmx3.googlemail.com2015-05-25 → 2026-02-15 · 3 obs
● 2015-05-25 13:57:48
● 2026-02-15 22:45:18
○ 2026-03-27 04:28:46
● 2026-02-15 22:45:18
○ 2026-03-27 04:28:46
○A104.198.14.522019-12-28 → 2019-12-28 · 4 obs
○ 2017-03-20 10:12:12
● 2019-12-28 22:52:30
○ 2026-02-15 22:45:18
○ 2026-03-27 04:28:46
● 2019-12-28 22:52:30
○ 2026-02-15 22:45:18
○ 2026-03-27 04:28:46
○A13.81.221.1972017-03-20 → 2017-03-20 · 4 obs
○ 2016-07-21 06:07:18
● 2017-03-20 10:12:12
○ 2019-12-28 22:52:30
○ 2026-03-27 04:28:46
● 2017-03-20 10:12:12
○ 2019-12-28 22:52:30
○ 2026-03-27 04:28:46
●A184.169.135.342026-02-15 → 2026-03-27 · 3 obs
○ 2019-12-28 22:52:30
● 2026-02-15 22:45:18
● 2026-03-27 04:28:46
● 2026-02-15 22:45:18
● 2026-03-27 04:28:46
●A52.8.178.1322026-02-15 → 2026-03-27 · 3 obs
○ 2019-12-28 22:52:30
● 2026-02-15 22:45:18
● 2026-03-27 04:28:46
● 2026-02-15 22:45:18
● 2026-03-27 04:28:46
○A95.128.203.112015-05-25 → 2016-07-21 · 4 obs
● 2015-05-25 13:57:48
● 2016-07-21 06:07:18
○ 2017-03-20 10:12:12
○ 2026-03-27 04:28:46
● 2016-07-21 06:07:18
○ 2017-03-20 10:12:12
○ 2026-03-27 04:28:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| de | a.nic.de, f.nic.de, z.nic.de | - |
| sensorberg.de | ns1.open-telekom-cloud.com, ns2.open-telekom-cloud.com | - |
✅ Authoritative Response
Server:93.188.242.252
NS records: ns1.open-telekom-cloud.com, ns2.open-telekom-cloud.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for sensorberg.de (unsigned zone)
⏱️ Timing
Total: 966ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.8.178.132, 184.169.135.34 |
| NS | 2 | ns1.open-telekom-cloud.com, ns2.open-telekom-cloud.com |
| SOA | 1 | ns1.open-telekom-cloud.com infrastructur |
Analysis
IP Addresses
sensorberg.de points to two IP numbers: 52.8.178.132 and 184.169.135.34.
Other host names such as advantageteamblog.com, www.lsvusa.com, webvolta.com, ajug.org and iaqanalytics.com share IPs with sensorberg.de.
Name Servers
Two name servers ns1.open-telekom-cloud.com and ns2.open-telekom-cloud.com handle the delegation for sensorberg.de.
sensorberg.de shares the same name server setup as other domains, for example 197.44.160.in-addr.arpa, infranaut.net, 34.158.80.in-addr.arpa, 21.158.80.in-addr.arpa and 14.30.164.in-addr.arpa.
Host names with one IP number:
ns1.open-telekom-cloud.com points to 80.158.48.19; ns2.open-telekom-cloud.com points to 93.188.242.252.