Use asterisks to match entire IP ranges without calculating CIDR prefixes
Not everyone speaks CIDR fluently. If you just want to block “anything starting with 192.168″—wildcards are your friend. One simple * symbol can replace hours of subnet calculations.
🎯 What Is a Wildcard Pattern?
A wildcard pattern uses the asterisk (*) symbol to represent “any value” in an IP address. Instead of specifying exact numbers, you let the asterisk match anything from 0 to 255.
🎯
The Asterisk
*
Matches any number from 0 to 255
✨
Example
192.168.1.*
Matches 677a618a@c077d2a1.com through 73c09fa0@69174c53.com
📐 Anatomy of a Wildcard Pattern
An IPv4 address has four “octets” (number groups) separated by dots. You can replace any octet with an asterisk:
192.168.*.*
🔒 Fixed octets🎯 Wildcard octets (0-255)
This pattern (192.168.*.*) would match:
192.168.0.1
192.168.50.100
192.168.255.255
192.168.1.1
But would NOT match:
192.167.1.1
10.0.0.1
193.168.1.1
172.16.0.1
📋 Valid Wildcard Patterns
WhoKnew Views™ supports wildcards in any position of an IPv4 address:
| Pattern | Matches | IPs Covered | Use Case |
|---|---|---|---|
| a73478ad@964c9d1f.com.* | 677a618a@c077d2a1.com – 73c09fa0@69174c53.com | 256 | Single subnet |
| 192.168.*.* | aa83ff20@a0fb640b.com – 25e712c2@7321dab3.com | 65,536 | Typical home/office network |
| 192.*.*.* | 192.0.0.0 – 61534ae8@ba1d2a30.com | 16.7M | Large network block |
| 10.*.*.* | 10.0.0.0 – 2de31193@198fbe81.com | 16.7M | All 10.x private IPs |
| 172.16.*.* | aa2f29f2@ea3f01d4.com – 5892d78c@46d67d30.com | 65,536 | Docker/Kubernetes networks |
⚙️ How Matching Works (Behind the Scenes)
When you enter a wildcard pattern, WhoKnew Views™ converts it to a regular expression for precise matching:
🔧 Pattern Transformation
Your Pattern:
→
Internal Regex:
/^192\.168\.1\.[0-9]+$/
Your Pattern:
10.*.*.*
→
Internal Regex:
/^10\.[0-9]+\.[0-9]+\.[0-9]+$/
Translation rules: The . becomes \. (literal dot) and * becomes [0-9]+ (one or more digits).
ℹ️ Note: You don’t need to understand regex—just use asterisks and WhoKnew Views™ handles the rest!
🚫 IPv4 Only — No IPv6 Wildcards
🚫
Wildcards Don’t Work with IPv6
IPv6 addresses are too complex for simple asterisk matching
❌2001:db8:*::*— Invalid! Will be rejected
❌fe80::*— Invalid! Will be rejected
✅2001:db8::/32— Use CIDR for IPv6 ranges
⚠️ Why IPv6 can’t use wildcards: IPv6 has 8 hexadecimal groups (like 2001:0db8:85a3:0000:0000:8a2e:0370:7334), and each group can contain letters and numbers. Simple asterisk matching would be ambiguous. CIDR notation provides precise, unambiguous range definitions.
🆚 Wildcards vs CIDR: When to Use Each
🎯 Use Wildcards When…
- You want quick, simple patterns
- You’re blocking IPv4 only
- You need full octet ranges (256 IPs per *)
- You don’t know CIDR notation
- Precision isn’t critical
📡 Use CIDR When…
- You need precise subnet control
- You’re blocking IPv6 ranges
- You want industry-standard notation
- You’re sharing configs with IT teams
- You need non-256 boundaries (e.g., /25 = 128 IPs)
📊 Quick Comparison Table
| Wildcard | ≈ | CIDR Equivalent |
|---|---|---|
| a73478ad@964c9d1f.com.* | = | 677a618a@c077d2a1.com/24 |
| 192.168.*.* | = | aa83ff20@a0fb640b.com/16 |
| 10.*.*.* | = | 10.0.0.0/8 |
| 172.16.*.* | = | aa2f29f2@ea3f01d4.com/16 |
🎨 Common Wildcard Recipes
📁 Copy-Paste Ready Patterns
192.168.*.*
🏠 Standard home router networks
65,536 IPs
10.*.*.*
🏢 Corporate internal networks
16.7M IPs
172.17.*.*
🐳 Docker default bridge network
65,536 IPs
📶 Single router subnet
256 IPs
⚠️ Validation Errors
If your wildcard pattern is invalid, WhoKnew Views™ will reject it with a helpful message:
"Wildcards not supported for IPv6. Use CIDR notation instead."
You tried using * in an IPv6 address—switch to CIDR
"Invalid wildcard IPv4 pattern"
The pattern doesn’t form a valid IPv4 structure (check dots and octets)
🔑 Key Takeaways
✅ Simple: Use * to replace any octet (number) in an IPv4 address
✅ Flexible: Put asterisks anywhere: *.168.1.1, 192.*.1.*, 10.*.*.*
✅ Fast: No CIDR math needed—just type and go
⚠️ IPv4 Only: For IPv6 ranges, you must use CIDR notation
⚠️ Full Octets: Each * matches 256 values—you can’t do partial ranges like “100-200”
🎯 Bottom Line
Wildcards are the easiest way to block IP ranges in WhoKnew Views™. If you don’t speak CIDR, don’t worry—just sprinkle some asterisks and you’re done!