Main

processing priority

4

site type

0 (generic, awaiting analysis)

review version

11

html import

20 (imported)

Events

first seen date

2023-12-27 10:09:05

expired found date

-

created at

2024-07-06 03:15:38

updated at

2025-06-03 05:00:36

Domain name statistics

length

14

crc

5415

tld

2211

nm parts

0

nm random digits

0

nm rare letters

0

Connections

is subdomain of id

198683790 (hersam.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)

Subdomains and pages

deleted subdomains

0

page imported products

0

page imported random

0

page imported parking

0

Error counters

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

server bits

server ip

-

Mainpage statistics

mp import status

20

mp rejected date

-

mp saved date

-

mp size orig

21991

mp size raw text

6267

mp inner links count

29

mp inner links status

10 (links queued, awaiting import)

Open Graph

title

description

Commentary on news, Linux, programming, music, web design, trivia, humor, usability and whatever else strikes his fancy at the time.

image

site name

author

Dan Hersam

updated

2026-02-27 20:40:47

raw text

Local Docker Port Exposed Amidst a tangled web Local Docker Port Exposed If you’re using docker with ufw (Ubuntu Firewall), your local ports may be exposed to the outside world. I recently read about this issue and when I checked, sure enough, the local ports of all of my docker containers were readily accessible. It felt like being caught with my fly down. Why in the world docker does this by default is beyond me. And it’s not as if they’re not aware of it. This GitHub issue clearly lays out the problem. It’s disappointing the issue has existed for so long and the Docker team isn’t willing to fix it. It’s a major violation of the secure by default principle. If you too are learning about this, here’s the fix. 1. Create /etc/docker/daemon.json if it doesn’t already exist 2. Add the following content to the file { "iptables": false } 3. Restart docker sudo service docker restart Who knows if there are other docker vulnerabilities I’m not aware of, but at leas...

Text analysis

redirect type

0 (-)

block type

0 (no issues)

detected language

1 (English)

category id

Serwisy SEC (10)

index version

1

spam phrases

0

Text statistics

text nonlatin

0

text cyrillic

0

text characters

4668

text words

1030

text unique words

528

text lines

138

text sentences

56

text paragraphs

16

text words per sentence

18

text matched phrases

0

text matched dictionaries

0

RSS

rss status

32 (unknown)

rss found date

2023-12-27 11:41:29

rss size orig

28556

rss items

10

rss spam phrases

0

rss detected language

1 (English)

inbefore feed id

-

inbefore status

0 (new)

Sitemap

sitemap status

34 (reserved: import paused pending content quality/relevance assessment after importing first 500 pages)

sitemap review version

2

sitemap urls count

1794

sitemap urls adult

0

sitemap filtered products

0

sitemap filtered videos

1

sitemap found date

2023-12-27 10:09:05

sitemap process date

2024-11-26 16:00:38

sitemap first import date

-

sitemap last import date

2025-06-03 05:00:36