Suspected cluster 40bef666f218ACTIVE
BetaShared-infrastructure grouping of public detections. Not an attribution claim.
Indicators
3Active
3Brands
1First seen
Mar 28Last activity
Jun 08 What these pages look like
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 apex
m365-microsoft.com
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
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 below. 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.
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
Indicators
security.m365-microsoft.com