Suspected cluster 40bef666f218ACTIVE
BetaShared-infrastructure grouping of public detections. Not an attribution claim.
Indicators
3Active
3Brands
1First seen
Mar 28, 2026Most recent detection
Jun 08, 2026 What these pages look like
Indicators
Why this confidence
60%
suspected cluster
Link strength
62%
Evidence diversity
100%
Time compactness
0%
Strong-link share
67%
Size discount
100%
confidence = clamp(0.45×D + 0.25×V + 0.20×T + 0.10×B, 0, 1) × S. Thresholds: 70%+ possible campaign, 40%+ suspected cluster.
Evidence summary
3/3
same TLS cert
747cef48fe4c39e1512b3afa2438066e0785066cbe7d04f869a240d3a7cd42c9
3/3
same favicon
97da6c23cbcc9492
3/3
same nameservers
ns1-36.azure-dns.com,ns2-36.azure-dns.net,ns3-36.azure-dns.org,ns4-36.azure-dns.info
3/3
same apex
m365-microsoft.com
3/3
similar name
m365
Brands targeted
Timeline (first seen)
Spread over 72 days
Mar 28
1
Jun 06
1
Jun 08
1
History
2026-07-18
shrank
-2 members, now 3
2026-07-18
created
first tracked with 5 indicators
Rebuilt daily; history is kept for 180 days. A campaign keeps its identifier as members join or leave.
How the members connect
| 1 | 2 | 3 | |
|---|---|---|---|
| 1 | 70 | 60 | |
| 2 | 70 | 56 | |
| 3 | 60 | 56 |
Each cell is the relationship score between two members, numbered as in the Indicators table above. Hover a cell for the domains and the signals behind it.
3 of 3 possible pairs are directly linked. A blank cell only means those two are not linked directly, they can still belong to the cluster through a third member.
Relationships
security.m365-microsoft.com ↔ support.m365-microsoft.com 70 first reproduced 2026-07-18
| Signal | Category | Contributed | IDF | Notes |
|---|---|---|---|---|
| same TLS cert | tls | 18.0 | - | |
| same screenshot | visual | 14.7 | - | |
| same nameservers | infra | 11.2 | ×0.80 | |
| same favicon | visual | 10.3 | ×0.80 | |
| same apex | infra | 8.0 | ×0.80 | |
| similar name | naming | 8.0 | ×0.80 |
Discounted observations
| same rare cert issuer | tls | 0.0 | - | cert_fingerprint_exact |
| shared TLS SAN | tls | 0.0 | - | cert_fingerprint_exact |
programme-hup.m365-microsoft.com ↔ security.m365-microsoft.com 60 first reproduced 2026-07-18
| Signal | Category | Contributed | IDF | Notes |
|---|---|---|---|---|
| same TLS cert | tls | 18.0 | - | |
| same nameservers | infra | 11.2 | ×0.80 | |
| same favicon | visual | 11.2 | ×0.80 | |
| same apex | infra | 8.0 | ×0.80 | |
| similar name | naming | 8.0 | ×0.80 | |
| appeared together (72h) | temporal | 4 | - |
Discounted observations
| same rare cert issuer | tls | 0.0 | - | cert_fingerprint_exact |
| shared TLS SAN | tls | 0.0 | - | cert_fingerprint_exact |
programme-hup.m365-microsoft.com ↔ support.m365-microsoft.com 56 first reproduced 2026-07-18
| Signal | Category | Contributed | IDF | Notes |
|---|---|---|---|---|
| same TLS cert | tls | 18.0 | - | |
| same nameservers | infra | 11.2 | ×0.80 | |
| same favicon | visual | 11.2 | ×0.80 | |
| same apex | infra | 8.0 | ×0.80 | |
| similar name | naming | 8.0 | ×0.80 |
Discounted observations
| same rare cert issuer | tls | 0.0 | - | cert_fingerprint_exact |
| shared TLS SAN | tls | 0.0 | - | cert_fingerprint_exact |
Infrastructure footprint
IP addresses
20.50.64.14
3/3
ASNs
8075
3/3
Hosting orgs
Registrars
Dynadot Inc
3/3
TLS certs
R13
3/3