id
related bits
0
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
2023-12-27 19:46:41
expired found date
-
created at
2024-07-06 13:41:02
updated at
2025-04-20 19:37:04
length
22
crc
19106
tld
2211
nm parts
0
nm random digits
0
nm rare letters
0
is subdomain of id
69893241 (blogspot.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
135198
mp size raw text
51282
mp inner links count
0
mp inner links status
1 (no links)
title
Errata Security
description
image
site name
author
updated
2026-02-23 07:05:00
raw text
Errata Security Errata Security Wednesday, February 01, 2023 C can be memory-safe The idea of memory-safe languages is in the news lately. C/C++ is famous for being the world's system language (that runs most things) but also infamous for being unsafe . Many want to solve this by hard-forking the world's system code, either by changing C/C++ into something that's memory-safe, or rewriting everything in Rust . Forking is a foolish idea. The core principle of computer-science is that we need to live with legacy, not abandon it. And there's no need. Modern C compilers already have the ability to be memory-safe, we just need to make minor -- and compatible -- changes to turn it on. Instead of a hard-fork that abandons legacy system, this would be a soft-fork that enables memory-safety for new systems. Consider the most recent memory-safety flaw in OpenSSL. They fixed it by first adding a memory-bounds , then putting every access to the memory behind a macro PUSHC() th...
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 nonlatin
0
text cyrillic
0
text characters
40598
text words
8248
text unique words
1996
text lines
554
text sentences
502
text paragraphs
156
text words per sentence
16
text matched phrases
3
text matched dictionaries
13
links self subdomains
0
links other subdomains
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
1 - coindesk.com
links ext booking
0
links ext news
3
links ext leaks
0
links ext ugc
41 - blogger.com, en.wikipedia.org, news.ycombinator.com, twitter.com
links ext klim
0
links ext generic
5
dol status
0
dol updated
2026-02-23 07:05:00
rss status
32 (unknown)
rss found date
2023-12-27 21:45:19
rss size orig
363843
rss items
25
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
1224
sitemap urls adult
0
sitemap filtered products
0
sitemap filtered videos
0
sitemap found date
2023-12-27 19:46:41
sitemap process date
2024-09-04 07:44:46
sitemap first import date
-
sitemap last import date
-