forumtree.com - dns.ninja

forumtree.com

DNSSEC⚠️ Not signed
A2606:4700:3035::6815:a93πŸ‡ΊπŸ‡Έ Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US βœ“ In HTTPS hints
A2606:4700:3037::ac43:8388πŸ‡ΊπŸ‡Έ Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US βœ“ In HTTPS hints
A104.21.10.147Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US βœ“ In HTTPS hints
A172.67.131.136πŸ‡ΊπŸ‡Έ Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US βœ“ In HTTPS hints
NSns1.domainmanage.com ⭐
A2400:cb00:2049:1::adf5:3b04πŸ‡ΊπŸ‡Έ Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street
A173.245.59.4πŸ‡ΊπŸ‡Έ Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns2.domainmanage.com
A2400:cb00:2049:1::c629:df27πŸ‡ΊπŸ‡Έ Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street
A198.41.223.39Cloudflare198.41.223.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRcf-198-41-223-39.cloudflare.com
HTTPSHTTP/3, HTTP/2 βœ“ hints match
IPv4 hints104.21.10.147, 172.67.131.136
IPv6 hints2606:4700:3035::6815:a93, 2606:4700:3037::ac43:8388
ECHX25519, HKDF-SHA256 + AES-128-GCM draft, id=116, name=cloudflare-ech.com
SOAns1.domainmanage.comdns@cloudflare.com serial=2408079427

com

Same first word

Similar names

DNS History

20 records (6 active, 14 former)

20162017201820192020202120222023202420252026NSns1.domainmanage.comns2.domainmanage.combuy.internettraffic.comns1.afternic.comns1.uniregistrymarket.linkns2.afternic.comns2.uniregistrymarket.linksell.internettraffic.comMXmx247.in-mx.commx247.in-mx.netA104.21.10.147172.67.131.1362606:4700:3035::6815:a932606:4700:3037::ac43:838813.248.169.482606:4700:3033::6815:a932606:4700:3033::ac43:838869.172.201.15369.172.201.20876.223.54.146
β—‹NSbuy.internettraffic.com2015-12-07 β†’ 2016-07-16 Β· 4 obs
● 2015-12-07 19:19:18
● 2016-07-16 23:30:48
β—‹ 2017-03-31 21:18:08
β—‹ 2026-08-10 20:02:00
β—‹NSns1.afternic.com2026-06-06 β†’ 2026-06-06 Β· 4 obs
β—‹ 2020-03-20 03:39:18
● 2026-06-06 19:36:28
β—‹ 2026-07-09 15:02:26
β—‹ 2026-08-10 20:02:00
●NSns1.domainmanage.com2026-07-09 β†’ 2026-08-10 Β· 3 obs
β—‹ 2026-06-06 19:36:28
● 2026-07-09 15:02:26
● 2026-08-10 20:02:00
β—‹NSns1.uniregistrymarket.link2017-03-31 β†’ 2020-03-20 Β· 5 obs
β—‹ 2016-07-16 23:30:48
● 2017-03-31 21:18:08
● 2020-03-20 03:39:18
β—‹ 2026-06-06 19:36:28
β—‹ 2026-08-10 20:02:00
β—‹NSns2.afternic.com2026-06-06 β†’ 2026-06-06 Β· 4 obs
β—‹ 2020-03-20 03:39:18
● 2026-06-06 19:36:28
β—‹ 2026-07-09 15:02:26
β—‹ 2026-08-10 20:02:00
●NSns2.domainmanage.com2026-07-09 β†’ 2026-08-10 Β· 3 obs
β—‹ 2026-06-06 19:36:28
● 2026-07-09 15:02:26
● 2026-08-10 20:02:00
β—‹NSns2.uniregistrymarket.link2017-03-31 β†’ 2020-03-20 Β· 5 obs
β—‹ 2016-07-16 23:30:48
● 2017-03-31 21:18:08
● 2020-03-20 03:39:18
β—‹ 2026-06-06 19:36:28
β—‹ 2026-08-10 20:02:00
β—‹NSsell.internettraffic.com2015-12-07 β†’ 2016-07-16 Β· 4 obs
● 2015-12-07 19:19:18
● 2016-07-16 23:30:48
β—‹ 2017-03-31 21:18:08
β—‹ 2026-08-10 20:02:00
β—‹MXmx247.in-mx.com2020-03-20 β†’ 2020-03-20 Β· 3 obs
● 2020-03-20 03:39:18
β—‹ 2026-06-06 19:36:28
β—‹ 2026-08-10 20:02:00
β—‹MXmx247.in-mx.net2020-03-20 β†’ 2020-03-20 Β· 3 obs
● 2020-03-20 03:39:18
β—‹ 2026-06-06 19:36:28
β—‹ 2026-08-10 20:02:00
●A104.21.10.1472026-07-09 β†’ 2026-08-10 Β· 3 obs
β—‹ 2026-06-06 19:36:28
● 2026-07-09 15:02:26
● 2026-08-10 20:02:00
β—‹A13.248.169.482026-06-06 β†’ 2026-06-06 Β· 4 obs
β—‹ 2020-03-20 03:39:18
● 2026-06-06 19:36:28
β—‹ 2026-07-09 15:02:26
β—‹ 2026-08-10 20:02:00
●A172.67.131.1362026-07-09 β†’ 2026-08-10 Β· 3 obs
β—‹ 2026-06-06 19:36:28
● 2026-07-09 15:02:26
● 2026-08-10 20:02:00
β—‹A2606:4700:3033::6815:a932026-07-09 β†’ 2026-07-09 Β· 3 obs
β—‹ 2026-06-06 19:36:28
● 2026-07-09 15:02:26
β—‹ 2026-08-10 20:02:00
β—‹A2606:4700:3033::ac43:83882026-07-09 β†’ 2026-07-09 Β· 3 obs
β—‹ 2026-06-06 19:36:28
● 2026-07-09 15:02:26
β—‹ 2026-08-10 20:02:00
●A2606:4700:3035::6815:a932026-08-10 β†’ 2026-08-10 Β· 2 obs
β—‹ 2026-07-09 15:02:26
● 2026-08-10 20:02:00
●A2606:4700:3037::ac43:83882026-08-10 β†’ 2026-08-10 Β· 2 obs
β—‹ 2026-07-09 15:02:26
● 2026-08-10 20:02:00
β—‹A69.172.201.1532016-07-16 β†’ 2020-03-20 Β· 5 obs
β—‹ 2016-03-17 04:14:32
● 2016-07-16 23:30:48
● 2020-03-20 03:39:18
β—‹ 2026-06-06 19:36:28
β—‹ 2026-08-10 20:02:00
β—‹A69.172.201.2082015-12-07 β†’ 2016-03-17 Β· 4 obs
● 2015-12-07 19:19:18
● 2016-03-17 04:14:32
β—‹ 2016-07-16 23:30:48
β—‹ 2026-08-10 20:02:00
β—‹A76.223.54.1462026-06-06 β†’ 2026-06-06 Β· 4 obs
β—‹ 2020-03-20 03:39:18
● 2026-06-06 19:36:28
β—‹ 2026-07-09 15:02:26
β—‹ 2026-08-10 20:02:00

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
forumtree.comns1.domainmanage.com, ns2.domainmanage.com2 records

βœ… Authoritative Response

Server:198.41.223.39

NS records: ns1.domainmanage.com, ns2.domainmanage.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for forumtree.com (unsigned zone)

⏱️ Timing

Total: 202ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A2172.67.131.136, 104.21.10.147
AAAA22606:4700:3035::6815:a93, 2606:4700:3037::ac43:8388
NS2ns1.domainmanage.com, ns2.domainmanage.com
HTTPS1{"priority":1,"target":".","alpn":["h3",
SOA1ns1.domainmanage.com dns.cloudflare.com

πŸ“Œ Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.domainmanage.com, ns2.domainmanage.com)

Analysis

IP Addresses

forumtree.com points to the four IP addresses 104.21.10.147, 172.67.131.136, 2606:4700:3035::6815:a93 and 2606:4700:3037::ac43:8388.

teambarakah.ca, wanderlustsoulmates.com, foroxd.com and two other host names share IP numbers with forumtree.com.

Name Servers

forumtree.com has two authoritative name servers β€” ns1.domainmanage.com and ns2.domainmanage.com.

forumtree.com uses the same name servers as several other domains β€” among them ruvo.net, idea(0x736578)po.com, plannews.com and two more.

The name servers for forumtree.com overlap at least partially with those of other domains β€” for example domainmanage.com.

Both ns1.domainmanage.com and ns2.domainmanage.com have two IP addresses each. ns1.domainmanage.com resolves to 173.245.59.4 and 2400:cb00:2049:1::adf5:3b04; ns2.domainmanage.com resolves to 198.41.223.39 and 2400:cb00:2049:1::c629:df27.