`physiokollmann.com`

DNSSEC	⚠️ Not signed
A	172.66.0.70^{🇺🇸 Cloudflare172.66.0.0/22 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`dns1.registrar-servers.com` ⭐
		A	2610:a1:1024::200^{🇺🇸 MAINT-ID-120082610:a1:1024::/48 Neustar}
			PTR	`dns1.namecheaphosting.com`
			PTR	`dns1.registrar-servers.com`
		A	156.154.132.200^{🇺🇸 MAINT-ID-12008156.154.132.0/24 Neustar}
			PTR	`dns1.namecheaphosting.com`
			PTR	`dns1.registrar-servers.com`
NS	`dns2.registrar-servers.com`
		A	2610:a1:1025::200^{🇺🇸 MAINT-ID-120082610:a1:1025::/48 Neustar}
			PTR	`dns2.namecheaphosting.com`
			PTR	`dns2.registrar-servers.com`
		A	156.154.133.200^{🇺🇸 MAINT-ID-12008156.154.133.0/24 Neustar}
			PTR	`dns2.namecheaphosting.com`
			PTR	`dns2.registrar-servers.com`
MX	`mx2.zoho.eu` ⭐
		A	89.36.170.166^{🇨🇭 COMPUTERLINE89.36.170.0/24}
			PTR	`mx2.zoho.eu`
			PTR	`mx3.zoho.eu`
			PTR	`mx.zoho.eu`
MX	`mx3.zoho.eu`⁽²⁰⁾
		A	185.230.212.166^{🇳🇱 ZOHO-EU185.230.212.0/23}
			PTR	`mx2.zoho.eu`
			PTR	`mx3.zoho.eu`
			PTR	`mx.zoho.eu`
MX	`mx.zoho.eu`⁽⁵⁰⁾
		A	185.230.212.166^{🇳🇱 ZOHO-EU185.230.212.0/23}
			PTR	`mx2.zoho.eu`
			PTR	`mx3.zoho.eu`
			PTR	`mx.zoho.eu`
		A	185.230.214.166^{🇳🇱 ZOHO-EU185.230.214.0/23}
			PTR	`mx2.zoho.eu`
			PTR	`mx3.zoho.eu`
			PTR	`mx.zoho.eu`
TXT	`v=spf1 include:zohomail.eu ~all`
SOA	`dns1.registrar-servers.com`hostmaster@registrar-servers.com serial=1773924135

`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.net`nstld@verisign-grs.com serial=1774378472

Same first word

physiokollmann.com

DNS History

23 records (6 active, 17 former)

○NSdns1.p03.nsone.net2018-01-13 → 2018-01-13 · 3 obs

○ 2016-12-20 22:28:50
● 2018-01-13 11:42:48
○ 2026-03-24 19:03:48

●NSdns1.registrar-servers.com2026-03-24 → 2026-03-24 · 2 obs

○ 2018-01-13 11:42:48
● 2026-03-24 19:03:48

○NSdns2.p03.nsone.net2018-01-13 → 2018-01-13 · 3 obs

○ 2016-12-20 22:28:50
● 2018-01-13 11:42:48
○ 2026-03-24 19:03:48

●NSdns2.registrar-servers.com2026-03-24 → 2026-03-24 · 2 obs

○ 2018-01-13 11:42:48
● 2026-03-24 19:03:48

○NSdns3.p03.nsone.net2018-01-13 → 2018-01-13 · 3 obs

○ 2016-12-20 22:28:50
● 2018-01-13 11:42:48
○ 2026-03-24 19:03:48

○NSdns4.p03.nsone.net2018-01-13 → 2018-01-13 · 3 obs

○ 2016-12-20 22:28:50
● 2018-01-13 11:42:48
○ 2026-03-24 19:03:48

○NSns-cloud-c1.googledomains.com2026-03-24 → 2026-03-24 · 1 obs

○ 2026-03-24 19:03:48

○NSns-cloud-c2.googledomains.com2026-03-24 → 2026-03-24 · 1 obs

○ 2026-03-24 19:03:48

○NSns-cloud-c3.googledomains.com2026-03-24 → 2026-03-24 · 1 obs

○ 2026-03-24 19:03:48

○NSns-cloud-c4.googledomains.com2026-03-24 → 2026-03-24 · 1 obs

○ 2026-03-24 19:03:48

○NSns1.systemdns.com2016-12-20 → 2016-12-20 · 3 obs

● 2016-12-20 22:28:50
○ 2018-01-13 11:42:48
○ 2026-03-24 19:03:48

○NSns2.systemdns.com2016-12-20 → 2016-12-20 · 3 obs

● 2016-12-20 22:28:50
○ 2018-01-13 11:42:48
○ 2026-03-24 19:03:48

○NSns3.systemdns.com2016-12-20 → 2016-12-20 · 3 obs

● 2016-12-20 22:28:50
○ 2018-01-13 11:42:48
○ 2026-03-24 19:03:48

●MXmx.zoho.eu2026-03-24 → 2026-03-24 · 1 obs

● 2026-03-24 19:03:48

●MXmx2.zoho.eu2026-03-24 → 2026-03-24 · 1 obs

● 2026-03-24 19:03:48

●MXmx3.zoho.eu2026-03-24 → 2026-03-24 · 1 obs

● 2026-03-24 19:03:48

●A172.66.0.702026-03-24 → 2026-03-24 · 2 obs

○ 2018-01-13 11:42:48
● 2026-03-24 19:03:48

○A198.185.159.1442018-01-13 → 2018-01-13 · 3 obs

○ 2016-12-20 22:28:50
● 2018-01-13 11:42:48
○ 2026-03-24 19:03:48

○A198.185.159.1452018-01-13 → 2018-01-13 · 3 obs

○ 2016-12-20 22:28:50
● 2018-01-13 11:42:48
○ 2026-03-24 19:03:48

○A198.49.23.1442016-12-20 → 2018-01-13 · 3 obs

● 2016-12-20 22:28:50
● 2018-01-13 11:42:48
○ 2026-03-24 19:03:48

○A198.49.23.1452018-01-13 → 2018-01-13 · 3 obs

○ 2016-12-20 22:28:50
● 2018-01-13 11:42:48
○ 2026-03-24 19:03:48

○A23.227.38.722026-03-24 → 2026-03-24 · 1 obs

○ 2026-03-24 19:03:48

○A2620:127:f00f:c::2026-03-24 → 2026-03-24 · 1 obs

○ 2026-03-24 19:03:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, k.gtld-servers.net, h.gtld-servers.net, b.gtld-servers.net...	-
physiokollmann.com	dns1.registrar-servers.com, dns2.registrar-servers.com	4 records

✅ Authoritative Response

Server:156.154.132.200

NS records: dns1.registrar-servers.com, dns2.registrar-servers.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for physiokollmann.com (unsigned zone)

⏱️ Timing

Total: 232ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`172.66.0.70`
NS	2	`dns1.registrar-servers.com, dns2.registrar-servers.com`
MX	3	`mx.zoho.eu (pri: 10), mx2.zoho.eu (pri: 20)...`
TXT	1	`v=spf1 include:zohomail.eu ~all`
SOA	1	`dns1.registrar-servers.com hostmaster.re`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)

Analysis

IP Addresses

physiokollmann.com points to IP number 172.66.0.70.

For instance, other host names s8n.ru, mailin2.bitcoinmena.sk, simplysing.ca, pixl.biz and tinyedc.com share IP numbers with physiokollmann.com.

Name Servers

physiokollmann.com is delegated to two name servers: dns1.registrar-servers.com and dns2.registrar-servers.com.

physiokollmann.com uses the same name server setup as other domains such as webgurus11.com, gandhis.com, klopprichards.com, asdjkqqwea.online and devthestyle.com.

physiokollmann.com shares name servers with other domains at least partially, for example pilone.us, evieg.com, wheresmrboo.com, ericdanielson.info and fpclaporte.church.