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-08-26 23:35:10
expired found date
-
created at
2024-08-26 23:35:10
updated at
2026-01-07 20:41:34
length
29
crc
52896
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
155505
mp size raw text
20742
mp inner links count
61
mp inner links status
10 (links queued, awaiting import)
title
Azure DevSecOps
description
image
site name
Azure DevSecOps
author
updated
2026-02-26 00:30:00
raw text
Azure DevSecOps Azure DevSecOps Skip to content Home About Contact Videos Open Source ← Older posts Tip: APIM self-hosted gateway in K8s and ip-filter policies Posted on 18 August 2020 by Stephane Eyskens If you happen to host the self-hosted gateway from Azure API Management into Kubernetes, pay attention to the default deployment script proposed by default on the Azure Portal. This deployment creates a K8s service of type LoadBalancer which are source NAT’d by default. This means that the ip-filter policy is totally useless in APIM policies with that config since the original source IP of the intermediate calling service (Say Azure Application Gateway or Front Door) will be lost. The original IP is still retrievable from the X-Forwarded-For HTTP header but if you want to make sure your gateway is proxied by a WAF, you have no way to control it other then with an ip-filter policy. This behavior is well described in the K8s doc https://kubernetes.io/do...
redirect type
0 (-)
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
16053
text words
3199
text unique words
1061
text lines
386
text sentences
116
text paragraphs
34
text words per sentence
27
text matched phrases
0
text matched dictionaries
0
links self subdomains
0
links other subdomains
links other domains
2 - kubernetes.io
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
31 - s0.wp.com, wp.me, s1.wp.com, wordpress.com, en.wikipedia.org, twitter.com
links ext klim
0
links ext generic
1
dol status
0
dol updated
2026-02-26 00:30:00
rss status
32 (unknown)
rss found date
2024-11-13 06:04:45
rss size orig
15972
rss items
10
rss spam phrases
0
rss detected language
1 (English)
inbefore feed id
-
inbefore status
0 (new)
sitemap path
sitemap status
40 (completed successful import of reports.txt file to table in_pages)
sitemap review version
2
sitemap urls count
117
sitemap urls adult
0
sitemap filtered products
1
sitemap filtered videos
1
sitemap found date
2024-09-01 11:36:36
sitemap process date
2024-09-01 11:36:37
sitemap first import date
-
sitemap last import date
2026-01-07 20:41:34