`codeberg-142.in-berlin.de`

DNSSEC	⚠️ Not signed
A	217.197.84.142^{🇩🇪 IN-BERLIN-AS217.197.80.0/20 Individual Network Berlin e.V.}
		PTR	`codeberg-142.in-berlin.de`

`in-berlin.de`

	DNSSEC	⚠️ Not signed
	A	2001:67c:1400:1010::11^{🇩🇪 IN-BERLIN-AS2001:67c:1400::/45 Individual Network Berlin e.V.}
	A	217.197.80.11^{🇩🇪 IN-BERLIN-AS217.197.80.0/20 Individual Network Berlin e.V.}
	NS	`ns1.in-berlin.de` ⭐
	NS	`ns2.in-berlin.de`
	NS	`ns3.in-berlin.de`
	NS	`ns4.in-berlin.de`
	MX	`mx1.in-berlin.de` ⭐
	MX	`mx2.in-berlin.de`⁽²⁰⁾
	MX	`mx3.in-berlin.de`⁽³⁰⁾
	MX	`mx4.in-berlin.de`⁽⁴⁰⁾
	TXT	`IN-Berlin e.V.`
	TXT	`v=spf1 include:_spf.in-berlin.de a:backend.nic-direct.de a:mail.vautron.de -all`
	SOA	`ns1.in-berlin.de`domain@in-berlin.de 2026-07-07 #20

WOT: SAFE (60/100)
rank #53168 globally
rank #1468 in the tld
WOT: SAFE (64/100)
📈 Tranco rank: #27,101

PTR for

142.84.197.217.in-addr.arpa

Same first word

codeberg-142.in-berlin.de

DNS History

1 record (1 active, 0 former)

●A217.197.84.1422026-04-07 → 2026-07-10 · 2 obs

● 2026-04-07 00:21:58
● 2026-07-10 06:19:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
de	a.nic.de, f.nic.de, z.nic.de	-
in-berlin.de	ns1.in-berlin.de, ns2.in-berlin.de, ns3.in-berlin.de, ns4.in-berlin.de	7 records

✅ Authoritative Response

Server:217.197.80.34

NS records: ns1.in-berlin.de, ns2.in-berlin.de, ns3.in-berlin.de, ns4.in-berlin.de

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for in-berlin.de (unsigned zone)

⏱️ Timing

Total: 731ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`217.197.84.142`

📌 Glue Records Collected

Total: 7

In-bailiwick: 7 (ns1.in-berlin.de, ns2.in-berlin.de, ns3.in-berlin.de...)

Analysis

IP Addresses

codeberg-142.in-berlin.de directs to one IP number, which is 217.197.84.142.

Host names such as codeberg-test.org and vip3.s.codeberg.org share IP numbers with codeberg-142.in-berlin.de.

codeberg-142.in-berlin.de - robtex.com