id
processing priority
4
site type
3 (personal blog or private political site, e.g. Blogspot, Substack, also small blogs on own domains)
review version
11
html import
20 (imported)
first seen date
2024-10-21 15:24:44
expired found date
-
created at
2024-10-21 15:24:44
updated at
2025-04-24 01:17:01
length
19
crc
48154
tld
2211
nm parts
0
nm random digits
0
nm rare letters
0
is subdomain of id
13642151 (wordpress.com)
previous id
0
replaced with id
0
related id
-
dns primary id
0
dns alternative id
0
lifecycle status
0 (unclassified, or currently active)
deleted subdomains
0
page imported products
0
page imported random
0
page imported parking
0
count skipped due to recent timeouts on the same server IP
0
count content received but rejected due to 11-799
0
count dns errors
0
count cert errors
0
count timeouts
0
count http 429
0
count http 404
0
count http 403
0
count http 5xx
0
next operation date
-
server bits
—
server ip
-
mp import status
20
mp rejected date
-
mp saved date
-
mp size orig
114934
mp size raw text
13281
mp inner links count
0
mp inner links status
1 (no links)
title
Good Workaround!
description
image
site name
Good Workaround!
author
updated
2026-02-22 15:24:00
raw text
Good Workaround! Skip to content Good Workaround! Issuing Custom Security Attributes in Entra ID tokens Custom security attributes in Entra ID is a feature that allows you to add attribute sets and attributes to your tenant, which you can use on all your user and application objects. A fairly common ask in Entra ID is the ability to store “secret data”, such as social security numbers, and making sure only certain principals can read these values. Here is where custom security attributes come into play. You can add an attribute set “PersonalInformation” to your tenant, and add “SSN” as an attribute to this attribute set. You can then tag each user with values, which only will be readable by those assigned the “Attribute assignment reader” role on tenant level or attribute set level. However, currently Entra ID does not allow for these to be a part of issued tokens, not part of outbound synchronization rules and not as criteria for criteria based groups. So yeah, not really ...
redirect type
30 (window.location)
block type
0 (no issues)
detected language
1 (English)
category id
index version
1
spam phrases
0
text nonlatin
0
text cyrillic
0
text characters
10016
text words
1950
text unique words
611
text lines
227
text sentences
73
text paragraphs
28
text words per sentence
26
text matched phrases
0
text matched dictionaries
0
links self subdomains
0
links other subdomains
0
links other domains
links spam adult
0
links spam random
0
links spam expired
0
links ext activities
0
links ext ecommerce
0
links ext finance
0
links ext crypto
0
links ext booking
0
links ext news
0
links ext leaks
0
links ext ugc
27 - s0.wp.com, wp.me, s1.wp.com, gwrnd.files.wordpress.com, twitter.com, wordpress.com
links ext klim
0
links ext generic
3
dol status
0
dol updated
2026-02-22 15:24:00
rss status
32 (unknown)
rss found date
2024-10-21 15:24:47
rss size orig
324851
rss items
10
rss spam phrases
0
rss detected language
1 (English)
inbefore feed id
-
inbefore status
0 (new)
sitemap path
sitemap status
30 (processing completed, results pushed to table crawler_sitemaps.ext_domain_sitemap_lists)
sitemap review version
1
sitemap urls count
127
sitemap urls adult
0
sitemap filtered products
0
sitemap filtered videos
0
sitemap found date
2024-10-21 15:24:45
sitemap process date
2024-10-21 15:24:46
sitemap first import date
-
sitemap last import date
-