Main

processing priority

4

site type

0 (generic, awaiting analysis)

review version

11

html import

20 (imported)

Events

first seen date

2024-08-28 11:57:46

expired found date

-

created at

2024-08-28 11:57:46

updated at

2026-01-12 05:21:46

Domain name statistics

length

14

crc

3316

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

1

count dns errors

0

count cert errors

0

count timeouts

1

count http 429

0

count http 404

0

count http 403

1

count http 5xx

0

next operation date

2025-03-30 11:50:34

Server

server bits

server ip

-

Mainpage statistics

mp import status

20

mp rejected date

-

mp saved date

-

mp size orig

21902

mp size raw text

5287

mp inner links count

1

mp inner links status

20 (imported)

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-01-08 06:22:55

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

SEC and Crypto [en] (228)

index version

2025123101

spam phrases

0

Text statistics

text nonlatin

0

text cyrillic

0

text characters

4091

text words

885

text unique words

433

text lines

78

text sentences

49

text paragraphs

14

text words per sentence

18

text matched phrases

1

text matched dictionaries

5

RSS

rss status

32 (unknown)

rss found date

2025-03-18 13:42:13

rss size orig

28136

rss items

10

rss spam phrases

0

rss detected language

1 (English)

inbefore feed id

-

inbefore status

0 (new)

Sitemap

sitemap status

40 (completed successful import of reports.txt file to table in_pages)

sitemap review version

2

sitemap urls count

1793

sitemap urls adult

0

sitemap filtered products

0

sitemap filtered videos

1

sitemap found date

2025-03-18 13:42:14

sitemap process date

2025-04-01 02:43:08

sitemap first import date

-

sitemap last import date

2026-01-08 11:07:48