WOTD keywords are now searchable

https://regex.ingress.codes/wotd

New keywords are added daily.

Today we’re launching a new tool to help find keywords in passcodes.

It works the same way like the other one on the Internet but it’s actually updated!

Sometimes you just want to know what keywords are possible to help spot a pattern in a code. For example:

`te68o5erezim2tk8uf`

The regular expression to find a possible keyword would be:

`^[te68o5erezim2tk8uf]{8}$`

The `^`

and `$`

denote the beginning and end of a string, essentially a whole word.

The `[te68o5erezim2tk8uf]`

denotes to look for a character within the `[]`

.

The `{8}`

tells it to look for 8 of those characters, since the prefix/suffix are 5 characters each, there are 8 remaining for the keyword.

Trying this example out reveals the keyword to be `timezero`

, and we can now look for the full passcode:

te 68 o5 er ez im 2t k8 uf

`timezero`

can be seen highlighted and we see a pattern for the passcode: `ufk82timezero568te`

.

If a code presents itself with a clean distribution and a correlation between letters/numbers, you can sometimes use the tool to find a keyword.

`a8bdacc6ccbbbaabbabcabb6b0b1ccccccaab0`

would be split into pairs:

`a8 bd ac c6 cc bb ba ab ba bc ab b6 b0 b1 cc cc cc aa b0`

The pairs starting with `c`

are in the same position as where numbers go, and you can now safely assume everything in the middle is a keyword.

`bb ba ab ba bc ab b6 b0 b1`

Looking for repeated sets, we see that `ba`

and `ab`

are repeated in the keyword. Creating a regular expression for it:

`^.(.)(.)\1.\2...$`

The `.`

not enclosed in `()`

denote any character we don’t generally care about.

The `(.)`

are captured to be reused in another part of the expression with `\1`

, `\2`

, etc., in the order in which they were captured.

With our example, we see the only result being `detection`

. If we compare the (uppercase) hexadecimal values of `detection`

to the code:

`bb ba ab ba bc ab b6 b0 b1`

`44 45 54 45 43 54 49 4f 4e`

We can now deduce the code was ciphered with a hexadecimal-atbash.

`57 42 53 39 33 44 45 54 45 43 54 49 4f 4e 33 33 33 55 4f`

`WBS93DETECTION333UO`

We have observed a new passcode format in the Body in Brooklyn. A Cover-Up? post on June 16 2016.

The new passcode format is:

`xxx##keyword###xx`

`x`

are any letter from `a-z`

`#`

are numbers `2-9`

`keyword`

is a word related to Ingress (*our compiled list of keywords*)

At this time, we are not sure if this code will be used exclusively for daily codes from the Investigation Blog or will it be expanded to include Word of the Day and Ingress Report codes.

The Wargames series continued into Aegis Nova with 15 puzzles containing critical intel for the agent who solves them. Verum Inveniri started off the festivities just before 1200 UTC and the first 10 puzzles all being unlocked within 90 minutes. At 2200 UTC, Verum Inveniri announced more challenges to bring the total to 15.

Remember, all the codes for this series eventually solve to the format `xxxxxxxx#keyword#`

(unless stated otherwise). This is a typical format for passcodes distributing volatile intel around anomalies.

*You’ve only witnessed one TENTH of my maximum mitigation!*

Solution

*Base your next step on what you gauge the numbers to mean.*

Solution

*Find the intersection between mathematics and local geography.*

Solution

*You should Investigate this further.*

Solution

*When were these Shields made anyway?*

Solution

*Between 7 and 16, Phoebus scored 15 touchdowns.*

Solution

*17, 18, 13, 20 are the first four rolls of a skilled Magic Missile caster.*

Solution

*Pad both the forward and aft parts of your ship.*

Solution

Look to IEEE 802.3 for the correct encoding.

Solution

Might have to make an international call for this one.

Solution

Can a bear play music?

Solution

Divided, we are united.

Solution

What does dinheiro mean?

Solution

*Alphabetic ancestor of Latin*

Solution

EOF

Solution

There are 6 codes found in the Klue’s Nightmares and her Dream post on the Investigation Blog. Normally there are only 3 codes found but there are 3 codes found in the image which was recycled from November 2014. 1, 2, and 3 are found in the source code; 4, 5, and 6 were found in the image.

`mcrhuq.wayzlsywfli.qeobbs.rumd`

`gsncftwgsiwtrevowevdrosik`

`hrxnotznitermatsixvmmthr`

Welcome to the world of Ingress passcode solving. By checking out this tutorial, you’ve taken the first step to ascend beyond the ranks of a field agent.

In this tutorial series, we’ll be going through a few basic topics, we’ll be adding more topics as they are written.

This post will discuss where to look for codes.

There were 2 codes found in the Jahan’s Denial post on the Investigation Blog.

`[1] oppr5evp794cpwu`

[2] ::;”””‘:”;’;;””‘:;”;;:’:”:””::”‘”‘;””:””;’;;’;””;:;”:;;:'””;'”‘;'”;:””:”;”‘;;;:”””:”’:””;:”::”:;;’;’:”‘”””;”:”;”‘

There were 3 codes found in the Oliver Lynton-Wolfe Missing post on the Investigation Blog.

`[1] [3qdq9h6r5w]`

[2] 204rm1qhe5n2r2j3ud

[3] htmamip3hseh27r2

There were 3 codes found on PAC’s Weekly Wrap-up post for April 10, 2016 on the Investigation Blog.

`[1] #%$&%)$*#$$%#^%)#^%^`

[2] lojlvlyr.rzbollpy

[3] 5664277766685664339911233393335776668222