berleaf.com - dns.ninja

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
TXTyandex-verification: 6a7bdf213439de98
TXTfacebook-domain-verification=aodxvengpgz68iqdtviittg2hhccdk
TXTv=spf1 redirect=_spf.yandex.net
SOAns1.digitalocean.comhostmaster@berleaf.com serial=0

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-06-28 21:46:16
β—‹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-06-28 21:46:16
●NSns1.digitalocean.com2017-01-22 β†’ 2026-06-28 Β· 3 obs
β—‹ 2016-04-08 05:44:36
● 2017-01-22 06:32:34
● 2026-06-28 21:46:16
●NSns2.digitalocean.com2017-01-22 β†’ 2026-06-28 Β· 3 obs
β—‹ 2016-04-08 05:44:36
● 2017-01-22 06:32:34
● 2026-06-28 21:46:16
●NSns3.digitalocean.com2017-01-22 β†’ 2026-06-28 Β· 3 obs
β—‹ 2016-04-08 05:44:36
● 2017-01-22 06:32:34
● 2026-06-28 21:46:16
β—‹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-06-28 21:46:16
β—‹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-06-28 21:46:16
β—‹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-06-28 21:46:16
●MXmx.yandex.net2026-02-26 β†’ 2026-06-28 Β· 3 obs
β—‹ 2017-01-22 06:32:34
● 2026-02-26 16:43:28
● 2026-06-28 21:46:16
β—‹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-06-28 21:46:16
β—‹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-06-28 21:46:16
●A174.138.28.1712026-02-26 β†’ 2026-06-28 Β· 3 obs
β—‹ 2018-06-05 22:27:24
● 2026-02-26 16:43:28
● 2026-06-28 21:46:16
β—‹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-06-28 21:46:16
β—‹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-06-28 21:46:16

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
berleaf.comns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com3 records

βœ… Authoritative Response

Server:172.64.49.209

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: 330ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A1174.138.28.171
NS3ns2.digitalocean.com, ns3.digitalocean.com...
MX1mx.yandex.net (pri: 10)
TXT3facebook-domain-verification=aodxvengpgz, v=spf1 redirect=_spf.yandex.net...
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 resolves to just one IP address, 174.138.28.171.

Name Servers

The authoritative name servers for berleaf.com are ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com β€” three in total.

berleaf.com shares at least some of its name servers with other domains, including tefarrow.com, smss.ro, concrete-patch.com and two others.

ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com all resolve to exactly two IP numbers apiece: ns1.digitalocean.com β†’ 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com β†’ 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com β†’ 172.64.49.209 and 2606:4700:52::ac40:31d1.

Mail Servers

The sole mail server for berleaf.com is mx.yandex.net.

Among the domains sharing a mail server setup with berleaf.com are firepss.ru, akorovkin.ru, domyland.ru and two others.

berleaf.com has at least some mail servers in common with other domains, such as skeo.ru, com-termo.ru, samogon-cheb.ru and kodbox.ru.

mx.yandex.net points to two IP addresses: 77.88.21.249 and 2a02:6b8::311.