medforth.de - dns.ninja

`medforth.de`

DNSSEC	🔒 Signed (DS record present)
A	2a02:2350:5:10c:803e:7932:8e11:f67f^{🇩🇰 ONECOM2a02:2350::/32 One.com A/S}
A	46.30.213.167^{🇩🇰 ONECOM46.30.208.0/21 One.com A/S}
NS	`ns01.one.com` ⭐
		A	2001:67c:28cc::10^{ONECOM-INFRA2001:67c:28cc::/48}
			PTR	`ns01.one.com`
		A	195.206.121.10^{ONECOM-INFRA195.206.121.0/24}
			PTR	`ns01.one.com`
NS	`ns02.one.com`
		A	2001:67c:3c0::10^{🇩🇰 ONECOM2001:67c:3c0::/48}
			PTR	`ns02.one.com`
		A	185.10.11.10^{ONECOM185.10.11.0/24}
			PTR	`ns02.one.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1d::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f26.1e100.net`
		A	172.253.63.27^{🇺🇸 Google172.253.63.0/24}
			PTR	`bi-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=JMPY73TIS219xv3vS1_tGBnuI2vM_aPRxPxNDUjWpqQ`
SOA	`ns01.one.com`hostmaster@one.com 2026-06-24 #5

`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.de`dns-operations@denic.de serial=1782467640

Same first word

medforth.de

medforth.me

medforth.com

Similar names

forthmed.com

forthmed.com.br

DNS History

17 records (9 active, 8 former)

●NSns01.one.com2026-02-22 → 2026-06-26 · 3 obs

○ 2017-03-26 10:03:42
● 2026-02-22 19:58:32
● 2026-06-26 10:01:10

●NSns02.one.com2026-02-22 → 2026-06-26 · 3 obs

○ 2017-03-26 10:03:42
● 2026-02-22 19:58:32
● 2026-06-26 10:01:10

○NSns1.jimdo.com2015-08-16 → 2017-03-26 · 4 obs

● 2015-08-16 00:15:42
● 2017-03-26 10:03:42
○ 2026-02-22 19:58:32
○ 2026-06-26 10:01:10

○NSns2.jimdo.com2015-08-16 → 2017-03-26 · 4 obs

● 2015-08-16 00:15:42
● 2017-03-26 10:03:42
○ 2026-02-22 19:58:32
○ 2026-06-26 10:01:10

●MXalt1.aspmx.l.google.com2026-02-22 → 2026-06-26 · 3 obs

○ 2017-03-26 10:03:42
● 2026-02-22 19:58:32
● 2026-06-26 10:01:10

●MXalt2.aspmx.l.google.com2026-02-22 → 2026-06-26 · 3 obs

○ 2017-03-26 10:03:42
● 2026-02-22 19:58:32
● 2026-06-26 10:01:10

●MXalt3.aspmx.l.google.com2026-02-22 → 2026-06-26 · 3 obs

○ 2017-03-26 10:03:42
● 2026-02-22 19:58:32
● 2026-06-26 10:01:10

●MXalt4.aspmx.l.google.com2026-02-22 → 2026-06-26 · 3 obs

○ 2017-03-26 10:03:42
● 2026-02-22 19:58:32
● 2026-06-26 10:01:10

●MXaspmx.l.google.com2026-02-22 → 2026-06-26 · 3 obs

○ 2017-03-26 10:03:42
● 2026-02-22 19:58:32
● 2026-06-26 10:01:10

○MXmx1.jimdo.com2015-08-16 → 2017-03-26 · 4 obs

● 2015-08-16 00:15:42
● 2017-03-26 10:03:42
○ 2026-02-22 19:58:32
○ 2026-06-26 10:01:10

○MXmx2.jimdo.com2015-08-16 → 2017-03-26 · 4 obs

● 2015-08-16 00:15:42
● 2017-03-26 10:03:42
○ 2026-02-22 19:58:32
○ 2026-06-26 10:01:10

●A2a02:2350:5:10c:803e:7932:8e11:f67f2026-02-22 → 2026-06-26 · 3 obs

○ 2017-03-26 10:03:42
● 2026-02-22 19:58:32
● 2026-06-26 10:01:10

●A46.30.213.1672026-02-22 → 2026-06-26 · 3 obs

○ 2017-03-26 10:03:42
● 2026-02-22 19:58:32
● 2026-06-26 10:01:10

○A54.171.1.42016-03-28 → 2016-03-28 · 4 obs

○ 2015-12-07 20:03:28
● 2016-03-28 06:20:44
○ 2017-03-26 10:03:42
○ 2026-06-26 10:01:10

○A54.229.122.2382015-12-07 → 2015-12-07 · 4 obs

○ 2015-08-16 00:15:42
● 2015-12-07 20:03:28
○ 2016-03-28 06:20:44
○ 2026-06-26 10:01:10

○A54.229.56.1132015-08-16 → 2015-08-16 · 3 obs

● 2015-08-16 00:15:42
○ 2015-12-07 20:03:28
○ 2026-06-26 10:01:10

○A54.76.77.2292017-03-26 → 2017-03-26 · 4 obs

○ 2016-03-28 06:20:44
● 2017-03-26 10:03:42
○ 2026-02-22 19:58:32
○ 2026-06-26 10:01:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
de	a.nic.de, f.nic.de, z.nic.de	-
medforth.de	ns01.one.com, ns02.one.com	-

✅ Authoritative Response

Server:195.206.121.10

NS records: ns01.one.com, ns02.one.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 2817ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`46.30.213.167`
AAAA	1	`2a02:2350:5:10c:803e:7932:8e11:f67f`
NS	2	`ns02.one.com, ns01.one.com`
MX	5	`alt3.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 1)...`
TXT	1	`google-site-verification=JMPY73TIS219xv3`
SOA	1	`ns01.one.com hostmaster.one.com`

Analysis

IP Addresses

medforth.de has two IP addresses: 46.30.213.167 and 2a02:2350:5:10c:803e:7932:8e11:f67f

Among the host names that share IP numbers with medforth.de are hrcichkeria.com, mail.livfuld.dk, 2measure.net and two others.

Name Servers

Two name servers handle the delegation for medforth.de: ns01.one.com and ns02.one.com.

medforth.de has the same name server delegation as a number of other domains, such as gotta.se, latencia.es, orsjon.se and two more.

medforth.de is at least partially co-delegated on name servers with other domains, such as kjehr.com.

ns01.one.com and ns02.one.com both carry two IP addresses. The A records for ns01.one.com are 195.206.121.10 and 2001:67c:28cc::10; the A records for ns02.one.com are 185.10.11.10 and 2001:67c:3c0::10.

Mail Servers

Five mail servers handle medforth.de: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

medforth.de shares at least some of its mail servers with other domains — for example tez.com, georgiaintrend.com, mountposition.co.jp and two more.

It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.

Hosts with two IP numbers each:

aspmx.l.google.com resolves to two addresses: 172.253.63.27 and 2607:f8b0:4004:c1d::1a.

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.27 and 2a00:1450:400c:c23::1a.