Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-tables-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/dumblittleman/public_html/wp-includes/functions.php on line 6121

Deprecated: Return type of IfwPsn_Vendor_Zend_Config::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Vendor/Zend/Config.php on line 248

Deprecated: Return type of IfwPsn_Vendor_Zend_Config::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Vendor/Zend/Config.php on line 258

Deprecated: Return type of IfwPsn_Vendor_Zend_Config::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Vendor/Zend/Config.php on line 278

Deprecated: Return type of IfwPsn_Vendor_Zend_Config::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Vendor/Zend/Config.php on line 269

Deprecated: Return type of IfwPsn_Vendor_Zend_Config::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Vendor/Zend/Config.php on line 304

Deprecated: Return type of IfwPsn_Vendor_Zend_Config::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Vendor/Zend/Config.php on line 292

Deprecated: Return type of IfwPsn_Wp_ORM_Idiorm::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 /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 1836

Deprecated: Return type of IfwPsn_Wp_ORM_Idiorm::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 /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 1840

Deprecated: Return type of IfwPsn_Wp_ORM_Idiorm::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 /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 1844

Deprecated: Return type of IfwPsn_Wp_ORM_Idiorm::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 /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 1851

Deprecated: Return type of IfwPsn_Wp_ORM_IdiormResultSet::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 2028

Deprecated: Return type of IfwPsn_Wp_ORM_IdiormResultSet::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 2037

Deprecated: Return type of IfwPsn_Wp_ORM_IdiormResultSet::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 2046

Deprecated: Return type of IfwPsn_Wp_ORM_IdiormResultSet::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 2055

Deprecated: Return type of IfwPsn_Wp_ORM_IdiormResultSet::offsetSet($offset, $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 /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 2064

Deprecated: Return type of IfwPsn_Wp_ORM_IdiormResultSet::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 2072

Deprecated: IfwPsn_Wp_ORM_IdiormResultSet implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 1985

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the remove_dashboard_access domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/dumblittleman/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-table-builder domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/dumblittleman/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/dumblittleman/public_html/wp-includes/functions.php on line 6121

Deprecated: Optional parameter $rowId declared before required parameter $tableId is implicitly treated as a required parameter in /home/dumblittleman/public_html/wp-content/plugins/ninja-tables-pro/src/TableEditor.php on line 345
Should You Be Googling Yourself?
Dumb Little Man

Should You Be Googling Yourself?

In 2004, after being shot by an unknown assailant, one Australian man encountered some disturbing information from Google search results. Revealed in image searches and even filled in by Google’s autocomplete searches was his own name, linked with the names of local criminals, mobsters to be exact.

This false information nearly cost him his very life. Yet, it was still plastered over the front page of Google search results begging the question – if it’s on Google, does it even matter if it’s true or not?

Do You Know What Google Says About You?

google news

Today, Google handles over 3.5 billion searches every day, a portion of which is simply folks searching for their own names. Millennials lead many previous generations in self-searches for reasons ranging from satisfying their curiosity to damage control.

Among Gen Zers, the younger post-millennial generation, more than one in ten even do so daily. Personal name inquiries to Google aren’t just a young person’s game, however; even boomers aren’t immune to the temptation.

Among the generations:

In Googling oneself, many people aren’t too happy with what they find, be it true information or otherwise. In fact, only one in five people who self-search actually find relevant and accurate information about themselves, most of it either outdated or in reference to a different person with the same name.

Common outcomes include:

What Does Incorrect Or Harmful Information Mean To You?

Though accounting for one very extreme case, the situation of this Australian man is something we should consider as a warning. The false information that was revealed to him, unfortunately, didn’t stop there, reminding us that what we can see when we search on Google for our own name is also what other people can see as well.

This can include potential employers, as they are the most likely to do a full background search, including a Google search, on their candidates. Cyber criminals are ever lurking in the shadows of the internet. For them, Google is a trove of valuable and potentially compromising information on their victims.

Americans love their social media and are willfully sharing more information about themselves than ever. That said, half of Americans also believe that their information is less secure than it was five years ago. But where do we point the finger other than towards ourselves?

Habits of oversharing come along with their own interpersonal annoyances, but very perceptive criminals and scammers see it as opportunity.

On Googling Yourself

On top of social media, two in three Americans use at least one other online secure account for managing personal data. All told, the average American frequents three different sites containing personal data. Though each account is (hopefully) protected with unique login credentials, including passwords, criminals can still use this information against you.

Much like slapping together a ransom note with letters cut from a magazine, cyber criminals know exactly where to look for information. All together, this creates a pretty comprehensive picture of a victim with information ranging from technical data, like account numbers or passwords, to personal information which include security question answers and even personality traits.

Among adults online:

Cyber criminals prey on vulnerable individuals from the very young, the very old to the very lonely. What we get is hyper-targeted cyber attacks from email phishing to dating site cat-fishing.

How secure is your information online?

The answer could be just a Google search away. Take control of your online data and keep it out of the wrong hands by Googling yourself on a regular basis.

Detailed in this infographic is the current state of online security, how far Google searches can really go, and what it takes to keep your online slate clean in the face of employers and criminals alike.

Source: SocialCatfish.com

Exit mobile version