Main

processing priority

3

site type

0 (generic, awaiting analysis)

review version

11

html import

20 (imported)

Events

first seen date

2024-04-09 08:04:54

expired found date

-

created at

2024-07-01 07:20:50

updated at

2024-07-02 11:14:30

Domain name statistics

length

8

crc

9355

tld

2265

nm parts

0

nm random digits

0

nm rare letters

0

Connections

is subdomain of id

-

previous id

0

replaced with id

0

related id

-

dns primary id

75337739

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

58159

mp size raw text

22245

mp inner links count

10

mp inner links status

10 (links queued, awaiting import)

Open Graph

title

description

image

site name

author

updated

2026-02-26 13:12:26

raw text

Giampaolo Rodola Giampaolo Rodola Python enthusiast, core developer, psutil author Blog Archives Donate Supporters About Newsletter Enter your email address to receive blog updates: Recognize connection errors Created: 16 mar 2023, Tags: python , socket , network Lately I've been dealing with an asynchronous TCP client app which sends messages to a remote server. Some of these messages are important, and cannot get lost. Because the connection may drop at any time, I had to implement a mechanism to resend the message once the client reconnects. As such, I needed a way to identify what constitutes a connection error . Python provides a builtin ConnectionError exception precisely for this purpose, but it turns out it's not enough. After observing logs in production, I found some errors that were not related to the socket connection per se, but rather to the system connectivity , like ENETUNREACH ("network unreachable") or ENETDO...

Text analysis

redirect type

0 (-)

block type

0 (no issues)

detected language

1 (English)

category id

Python i Perl (135)

index version

1

spam phrases

0

Text statistics

text nonlatin

0

text cyrillic

0

text characters

15571

text words

3317

text unique words

1102

text lines

837

text sentences

190

text paragraphs

36

text words per sentence

17

text matched phrases

0

text matched dictionaries

0

RSS

rss path

rss status

1 (priority 1 already searched, no matches found)

rss found date

-

rss size orig

0

rss items

0

rss spam phrases

0

rss detected language

0 (awaiting analysis)

inbefore feed id

-

inbefore status

0 (new)

Sitemap

sitemap path

sitemap status

1 (priority 1 already searched, no matches found)

sitemap review version

2

sitemap urls count

0

sitemap urls adult

0

sitemap filtered products

0

sitemap filtered videos

0

sitemap found date

-

sitemap process date

2024-07-01 07:20:50

sitemap first import date

-

sitemap last import date

-