kitchenlookbook.com - robtex.com

kitchenlookbook.com

DNSSEC⚠️ Not signed
A2001:19f0:c:e29:5400:4ff:fed4:65cf🇺🇸 AS-VULTR2001:19f0::/38 Vultr Assigned Prefix
A45.63.18.70🇺🇸 AS-VULTR45.63.16.0/21 Vultr Assigned Prefix
NSns1.vultr.com ⭐
A2001:19f0:ccc::1🇺🇸 AS-VULTR2001:19f0:ccc::/48 DNS1
A2001:19f0:ccd::1🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix
PTRns1.vultr.com
A173.199.96.96🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix
PTRns1.vultrusercontent.com
NSns1.wpdns.host
A2001:19f0:ccd::1🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix
PTRns1.vultr.com
A173.199.96.96🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix
PTRns1.vultrusercontent.com
NSns2.wpdns.host
A2001:19f0:ccd::2🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix
PTRns2.vultr.com
A173.199.96.97🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix
PTRns2.vultrusercontent.com
NSns3.wpdns.host
A2001:19f0:ccd::1🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix
PTRns1.vultr.com
A173.199.96.96🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix
PTRns1.vultrusercontent.com
SOAns1.vultr.comdnsadm@choopa.com serial=0

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1774549637

Same first word

kitchenlookbook.co.nz
kitchenlookbook.tempurl.host
kitchenlookbook.com

DNS History

20 records (6 active, 14 former)

2017201820192020202120222023202420252026NSns1.vultr.comns1.wpdns.hostns2.wpdns.hostns3.wpdns.hostns-uk.1and1-dns.bizns-uk.1and1-dns.co.ukns-uk.1and1-dns.comns-uk.1and1-dns.orgns1035.ui-dns.bizns1035.ui-dns.comns1035.ui-dns.dens1035.ui-dns.orgMXmx00.1and1.co.ukmx01.1and1.co.ukA2001:19f0:c:e29:5400:4ff:fed4:65cf45.63.18.702001:8d8:1000:90b2:1614:cd25:9208:78062001:8d8:1001:5090:f5a0:677:47d3:864212.227.247.12217.160.233.97
○NSns-uk.1and1-dns.biz2016-12-20 → 2016-12-20 · 3 obs
● 2016-12-20 22:16:28
○ 2017-12-28 09:51:28
○ 2026-03-26 18:33:54
○NSns-uk.1and1-dns.co.uk2016-12-20 → 2016-12-20 · 3 obs
● 2016-12-20 22:16:28
○ 2017-12-28 09:51:28
○ 2026-03-26 18:33:54
○NSns-uk.1and1-dns.com2016-12-20 → 2016-12-20 · 3 obs
● 2016-12-20 22:16:28
○ 2017-12-28 09:51:28
○ 2026-03-26 18:33:54
○NSns-uk.1and1-dns.org2016-12-20 → 2016-12-20 · 3 obs
● 2016-12-20 22:16:28
○ 2017-12-28 09:51:28
○ 2026-03-26 18:33:54
●NSns1.vultr.com2026-03-26 → 2026-03-26 · 2 obs
○ 2017-12-28 09:51:28
● 2026-03-26 18:33:54
●NSns1.wpdns.host2026-03-26 → 2026-03-26 · 2 obs
○ 2017-12-28 09:51:28
● 2026-03-26 18:33:54
○NSns1035.ui-dns.biz2017-12-28 → 2017-12-28 · 3 obs
○ 2016-12-20 22:16:28
● 2017-12-28 09:51:28
○ 2026-03-26 18:33:54
○NSns1035.ui-dns.com2017-12-28 → 2017-12-28 · 3 obs
○ 2016-12-20 22:16:28
● 2017-12-28 09:51:28
○ 2026-03-26 18:33:54
○NSns1035.ui-dns.de2017-12-28 → 2017-12-28 · 3 obs
○ 2016-12-20 22:16:28
● 2017-12-28 09:51:28
○ 2026-03-26 18:33:54
○NSns1035.ui-dns.org2017-12-28 → 2017-12-28 · 3 obs
○ 2016-12-20 22:16:28
● 2017-12-28 09:51:28
○ 2026-03-26 18:33:54
●NSns2.wpdns.host2026-03-26 → 2026-03-26 · 2 obs
○ 2017-12-28 09:51:28
● 2026-03-26 18:33:54
●NSns3.wpdns.host2026-03-26 → 2026-03-26 · 2 obs
○ 2017-12-28 09:51:28
● 2026-03-26 18:33:54
○MXmx00.1and1.co.uk2016-12-20 → 2017-12-28 · 3 obs
● 2016-12-20 22:16:28
● 2017-12-28 09:51:28
○ 2026-03-26 18:33:54
○MXmx01.1and1.co.uk2016-12-20 → 2017-12-28 · 3 obs
● 2016-12-20 22:16:28
● 2017-12-28 09:51:28
○ 2026-03-26 18:33:54
●A2001:19f0:c:e29:5400:4ff:fed4:65cf2026-03-26 → 2026-03-26 · 2 obs
○ 2017-12-28 09:51:28
● 2026-03-26 18:33:54
○A2001:8d8:1000:90b2:1614:cd25:9208:78062016-12-20 → 2016-12-20 · 3 obs
● 2016-12-20 22:16:28
○ 2017-12-28 09:51:28
○ 2026-03-26 18:33:54
○A2001:8d8:1001:5090:f5a0:677:47d3:8642017-12-28 → 2017-12-28 · 3 obs
○ 2016-12-20 22:16:28
● 2017-12-28 09:51:28
○ 2026-03-26 18:33:54
○A212.227.247.122017-12-28 → 2017-12-28 · 3 obs
○ 2016-12-20 22:16:28
● 2017-12-28 09:51:28
○ 2026-03-26 18:33:54
○A217.160.233.972016-12-20 → 2016-12-20 · 3 obs
● 2016-12-20 22:16:28
○ 2017-12-28 09:51:28
○ 2026-03-26 18:33:54
●A45.63.18.702026-03-26 → 2026-03-26 · 2 obs
○ 2017-12-28 09:51:28
● 2026-03-26 18:33:54

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coml.gtld-servers.net, c.gtld-servers.net, g.gtld-servers.net, k.gtld-servers.net...-
kitchenlookbook.comns1.wpdns.host, ns2.wpdns.host, ns3.wpdns.host-

✅ Authoritative Response

Server:173.199.96.96

NS records: ns1.wpdns.host, ns2.wpdns.host, ns3.wpdns.host

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for kitchenlookbook.com (unsigned zone)

⏱️ Timing

Total: 286ms | Queries: -

📄 Records

TypeCountSample Data
A145.63.18.70
AAAA12001:19f0:c:e29:5400:4ff:fed4:65cf
NS3ns1.wpdns.host, ns3.wpdns.host...
SOA1ns1.vultr.com dnsadm.choopa.com

Analysis

IP Addresses

kitchenlookbook.com resolves to two IPs: 2001:19f0:c:e29:5400:4ff:fed4:65cf and 45.63.18.70.

Other host names, for instance kitchenlookbook.tempurl.host, share IP numbers with kitchenlookbook.com.

Name Servers

kitchenlookbook.com is delegated to four name servers: ns1.vultr.com, ns1.wpdns.host, ns2.wpdns.host and ns3.wpdns.host.

kitchenlookbook.com at least partially shares name servers with other domains, for instance aflext.com, devthane.com, ificincy.org, vikingdigital.com and ewcole.com.

These name servers are commonly used with the name servers ns2.vultr.com.

Three IPs for ns1.vultr.com: ns1.vultr.com points to 2001:19f0:ccc::1, 2001:19f0:ccd::1 and 173.199.96.96.

Two IPs for ns1.wpdns.host: ns1.wpdns.host points to 2001:19f0:ccd::1 and 173.199.96.96.

Two IPs for ns2.wpdns.host: ns2.wpdns.host points to 2001:19f0:ccd::2 and 173.199.96.97.

Two IPs for ns3.wpdns.host: ns3.wpdns.host points to 2001:19f0:ccd::1 and 173.199.96.96.

Hosts pointing to 2001:19f0:ccd::1: ns1.vultr.com, ns1.wpdns.host and ns3.wpdns.host.

Hosts pointing to 173.199.96.96: ns1.vultr.com, ns1.wpdns.host and ns3.wpdns.host.