berleaf.com - robtex.com

berleaf.com

DNSSEC⚠️ Not signed
A174.138.28.171πŸ‡ΈπŸ‡¬ DIGITALOCEAN174.138.16.0/20 DigitalOcean
PTRubuntu-22.04.5-lts-x64
NSns1.digitalocean.com ⭐
A2606:4700:52::ac40:34d2πŸ‡ΊπŸ‡Έ Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns1.digitalocean.com
A172.64.52.210πŸ‡ΊπŸ‡Έ Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns1.digitalocean.com
NSns2.digitalocean.com
A2606:4700:5a::ac40:3515πŸ‡ΊπŸ‡Έ Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns2.digitalocean.com
A172.64.53.21πŸ‡ΊπŸ‡Έ Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns2.digitalocean.com
NSns3.digitalocean.com
A2606:4700:52::ac40:31d1πŸ‡ΊπŸ‡Έ Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns3.digitalocean.com
A172.64.49.209πŸ‡ΊπŸ‡Έ Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns3.digitalocean.com
MXmx.yandex.net ⭐
A2a02:6b8::311πŸ‡·πŸ‡Ί TELETECH2a02:6b8::/32 Yandex network
PTRmxfront.stable.qloud-b.yandex.net
A77.88.21.249πŸ‡·πŸ‡Ί TELETECH77.88.0.0/18 Yandex enterprise network
PTRmxfront.stable.qloud-b.yandex.net
TXTv=spf1 redirect=_spf.yandex.net
TXTyandex-verification: 6a7bdf213439de98
TXTfacebook-domain-verification=aodxvengpgz68iqdtviittg2hhccdk
SOAns1.digitalocean.comhostmaster@berleaf.com serial=1678754133

com

Same first word

Similar names

DNS History

14 records (5 active, 9 former)

20162017201820192020202120222023202420252026NSns1.digitalocean.comns2.digitalocean.comns3.digitalocean.comemma.ns.cloudflare.comnorm.ns.cloudflare.comns57.domaincontrol.comns58.domaincontrol.comMXmx.yandex.netmailstore1.secureserver.netsmtp.secureserver.netA174.138.28.171128.199.106.231209.141.56.12950.63.202.22
β—‹NSemma.ns.cloudflare.com2015-05-30 β†’ 2015-10-26 Β· 4 obs
● 2015-05-30 22:07:12
● 2015-10-26 04:40:28
β—‹ 2015-12-31 12:26:58
β—‹ 2026-03-26 17:31:54
β—‹NSnorm.ns.cloudflare.com2015-05-30 β†’ 2015-10-26 Β· 4 obs
● 2015-05-30 22:07:12
● 2015-10-26 04:40:28
β—‹ 2015-12-31 12:26:58
β—‹ 2026-03-26 17:31:54
●NSns1.digitalocean.com2017-01-22 β†’ 2026-03-26 Β· 3 obs
β—‹ 2016-04-08 05:44:36
● 2017-01-22 06:32:34
● 2026-03-26 17:31:54
●NSns2.digitalocean.com2017-01-22 β†’ 2026-03-26 Β· 3 obs
β—‹ 2016-04-08 05:44:36
● 2017-01-22 06:32:34
● 2026-03-26 17:31:54
●NSns3.digitalocean.com2017-01-22 β†’ 2026-03-26 Β· 3 obs
β—‹ 2016-04-08 05:44:36
● 2017-01-22 06:32:34
● 2026-03-26 17:31:54
β—‹NSns57.domaincontrol.com2015-12-31 β†’ 2016-04-08 Β· 5 obs
β—‹ 2015-10-26 04:40:28
● 2015-12-31 12:26:58
● 2016-04-08 05:44:36
β—‹ 2017-01-22 06:32:34
β—‹ 2026-03-26 17:31:54
β—‹NSns58.domaincontrol.com2015-12-31 β†’ 2016-04-08 Β· 5 obs
β—‹ 2015-10-26 04:40:28
● 2015-12-31 12:26:58
● 2016-04-08 05:44:36
β—‹ 2017-01-22 06:32:34
β—‹ 2026-03-26 17:31:54
β—‹MXmailstore1.secureserver.net2015-05-30 β†’ 2016-04-08 Β· 4 obs
● 2015-05-30 22:07:12
● 2016-04-08 05:44:36
β—‹ 2017-01-22 06:32:34
β—‹ 2026-03-26 17:31:54
●MXmx.yandex.net2026-02-26 β†’ 2026-03-26 Β· 3 obs
β—‹ 2017-01-22 06:32:34
● 2026-02-26 16:43:28
● 2026-03-26 17:31:54
β—‹MXsmtp.secureserver.net2015-05-30 β†’ 2016-04-08 Β· 4 obs
● 2015-05-30 22:07:12
● 2016-04-08 05:44:36
β—‹ 2017-01-22 06:32:34
β—‹ 2026-03-26 17:31:54
β—‹A128.199.106.2312017-01-22 β†’ 2018-06-05 Β· 5 obs
β—‹ 2016-04-08 05:44:36
● 2017-01-22 06:32:34
● 2018-06-05 22:27:24
β—‹ 2026-02-26 16:43:28
β—‹ 2026-03-26 17:31:54
●A174.138.28.1712026-02-26 β†’ 2026-03-26 Β· 3 obs
β—‹ 2018-06-05 22:27:24
● 2026-02-26 16:43:28
● 2026-03-26 17:31:54
β—‹A209.141.56.1292015-05-30 β†’ 2015-10-26 Β· 4 obs
● 2015-05-30 22:07:12
● 2015-10-26 04:40:28
β—‹ 2015-12-31 12:26:58
β—‹ 2026-03-26 17:31:54
β—‹A50.63.202.222015-12-31 β†’ 2016-04-08 Β· 5 obs
β—‹ 2015-10-26 04:40:28
● 2015-12-31 12:26:58
● 2016-04-08 05:44:36
β—‹ 2017-01-22 06:32:34
β—‹ 2026-03-26 17:31:54

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
comj.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net...-
berleaf.comns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com3 records

βœ… Authoritative Response

Server:172.64.53.21

NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for berleaf.com (unsigned zone)

⏱️ Timing

Total: 3106ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A1174.138.28.171
NS3ns3.digitalocean.com, ns1.digitalocean.com...
MX1mx.yandex.net (pri: 10)
TXT3v=spf1 redirect=_spf.yandex.net, yandex-verification: 6a7bdf213439de98...
SOA1ns1.digitalocean.com hostmaster.berleaf.

πŸ“Œ Glue Records Collected

Total: 3

Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)

Analysis

IP Addresses

berleaf.com points to a single IP: 174.138.28.171.

Name Servers

berleaf.com is delegated to three name servers: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.

berleaf.com partially shares name servers with other domains; examples include tefarrow.com, smss.ro, concrete-patch.com, 1.0.0.c.b.a.9.0.0.0.0.0.0.0.0.0.1.d.0.0.2.0.0.0.0.8.8.a.4.0.6.2.ip6.arpa and 35.198.143.in-addr.arpa.

Host names with two IP numbers:

ns1.digitalocean.com points to 2606:4700:52::ac40:34d2 and 172.64.52.210.

ns2.digitalocean.com points to 2606:4700:5a::ac40:3515 and 172.64.53.21.

ns3.digitalocean.com points to 2606:4700:52::ac40:31d1 and 172.64.49.209.

Mail Servers

berleaf.com is handled by a single mail server, mx.yandex.net.

berleaf.com has the same mail server setup as other domains, including firepss.ru, akorovkin.ru, abcdata.ru, egb.org.ru and ekbproje.com.

berleaf.com shares some mail servers with other domains at least partially, for example skeo.ru, com-termo.ru, samogon-cheb.ru and kodbox.ru.

Host mx.yandex.net resolves to two IPs: 2a02:6b8::311 and 77.88.21.249.