Router Naming Convention for datafoundry.net, 201904

Regular Expressions:

  1. ^[^\.]+\.([a-z]+\d+\..+)\.datafoundry\.net$

Statistics:

Legend:

Green

+ Inferred identifier, true positive when evaluated against training data

Orange

- Inferred identifier, false negative when evaluated against training data

Red

! Inferred identifier, false positive when evaluated against training data

Red

x Inferred identifier, but contains part of IP address literal embedded in hostname
~ False negative, not matched
o No regex matched the interface, but the interface was the only interface in this suffix on the router
* A filter regex matched the interface

Evaluation against training data:

colo1.aus1
207.207.35.186+po76.colo1.aus1.datafoundry.net
207.207.35.141+po81.colo1.aus1.datafoundry.net
216.166.79.41+tun0.colo1.aus1.datafoundry.net
209.99.121.5+v100.colo1.aus1.datafoundry.net
 
colo1.pod1.hou2
209.99.36.114+po2.colo1.pod1.hou2.datafoundry.net
209.99.36.118+po3.colo1.pod1.hou2.datafoundry.net
216.166.40.1216-166-40-1.fwd.datafoundry.com
 
colo1.pod1.tx1
207.207.35.162+po70.colo1.pod1.tx1.datafoundry.net
207.207.35.166+po71.colo1.pod1.tx1.datafoundry.net
 
colo1.pod1.tx2
206.127.10.34+po40.colo1.pod1.tx2.datafoundry.net
206.127.10.38+po41.colo1.pod1.tx2.datafoundry.net
 
colo1.pod3.tx1
207.207.35.178+po74.colo1.pod3.tx1.datafoundry.net
207.207.35.182+po75.colo1.pod3.tx1.datafoundry.net
 
colo2.aus1
207.207.35.190+po77.colo2.aus1.datafoundry.net
207.207.35.142+po81.colo2.aus1.datafoundry.net
 
colo3.aus1
207.207.35.194+po60.colo3.aus1.datafoundry.net
207.207.35.198+po61.colo3.aus1.datafoundry.net
 
ddos1.pod2.tx1
216.166.79.2+te3-1.ddos1.pod2.tx1.datafoundry.net
216.166.79.10+te3-3.ddos1.pod2.tx1.datafoundry.net
 
gw1.pod1.tx1
209.99.14.105+po10.gw1.pod1.tx1.datafoundry.net
209.66.92.122209.66.92.122.ipyx-085258-900-zyo.above.net
 
207.207.35.170-po72.colo1.pod2.tx1.datafoundry.net
207.207.35.174-po73.colo2.pod2.tx1.datafoundry.net
209.99.54.97209-99-54-97.fwd.datafoundry.com