Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/wildfac1/public_html/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/wildfac1/public_html/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/wildfac1/public_html/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/wildfac1/public_html/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/wildfac1/public_html/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated in /home1/wildfac1/public_html/wp-includes/Requests/Transport/cURL.php on line 345

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/wildfac1/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/wildfac1/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/wildfac1/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/wildfac1/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home1/wildfac1/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

Deprecated: http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated in /home1/wildfac1/public_html/wp-includes/Requests/Transport/cURL.php on line 345

Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /home1/wildfac1/public_html/wp-content/plugins/wordpress-seo/src/conditionals/third-party/elementor-edit-conditional.php on line 22

Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /home1/wildfac1/public_html/wp-content/plugins/wordpress-seo/src/conditionals/third-party/elementor-edit-conditional.php on line 28
Oriental Fire-Bellied Toad Facts
Deprecated: strtolower(): Passing null to parameter #1 ($string) of type string is deprecated in /home1/wildfac1/public_html/wp-content/plugins/wordpress-seo/src/generators/schema-generator.php on line 186
Original Wild Facts

Wild Fact #435 – Don’t Judge a Book by its Cover! – Oriental Fire-Bellied Toad

Oriental Fire-Bellied Toad
Photo from Wikimedia

Welcome back to another fun-filled week of Wild Facts. I hope you enjoyed your weekend and managed to get some rest, since we are heading to the other side of the world to look for the Oriental Fire-Bellied Toad, which exists in Korea, China and Russia. Similarly, we have managed to introduce this species to Beijing so that is a possible travel destination as well. One of the main lessons you should get out of today’s animal fact is that you really can’t judge a book by its cover. If you want to find out why, we will need to board our plane for Asia. So what are you waiting for?

So why can’t we judge a book by its cover? Well for starters, this toad species, isn’t actually a toad! Nope, they have bumpy skin like a common toad, however, they are actually a frog. Similarly, from above the Oriental Fire-Bellied Toad looks like a normal green frog with black spots, which is great for blending into their environment. The minute they perceive danger though, this frog will reveal their true colours. As a predator moves in the Fire-Bellied Toad will arch their back, and sometimes completely flip over, showing their bright red belly. Obviously, this bright colouration signals danger to the predator letting them know there is a good chance they will die if they try eating our froggy friend. See, what looked like a tasty snack turned out to be a possible deadly encounter!

Oriental Fire-Bellied Toad
Photo by Steven G. Johnson (Wikimedia)

So is the Oriental Fire-Bellied Toad bluffing or do they actually have a poison? This is the decision you would need to make if you are a predator and you better choose wisely since this particular “toad” isn’t bluffing. They will secrete a milky toxin from their skin, which is typically emitted from their legs or belly. Although, they are not the most toxic frog in the world, it is bad enough that I wouldn’t recommend eating them.

Are they harmful to humans? If ingested, the poison will cause some discomfort but for the most part, it won’t hurt humans too badly. Probably a good thing to know since the Oriental Fire-Bellied Toad is very popular in the pet trade. If you happen to own one then I highly recommend not handling it too much and make sure it is isolated from other frogs and toads. You don’t want them to be exposed to a poison all day long, right?

Well that does it for our first fact of the week. Enjoy the rest of your day and I will see you tomorrow.

Leave a Reply

Your email address will not be published.