dig-id.de bewertung und analyse

Robots.txt Information
Robot Path Permission
GoogleBot /
BingBot /
BaiduSpider /
YandexBot /
Meta Tags
Title Leif’s digital
Description Leif’s digital identity Loosely coupled computer gibberish Using SNTP time on Amiga May 23rd, 2021 I never really cared too much about having correct time
Keywords N/A
Server Information
WebSite dig-id favicondig-id.de
Host IP 185.26.156.210
Location Germany
Verwandte Websites
Site Rank
digi.xyz 0
Mehr zu entdecken
Site
firstwaters.de
beautyoase-perl.eu
tops.net
erminas.de
buehnenfotos.de
shakespeare-company.de
hgd-media.de
igl-labor.de
schlochau.de
koschneiderei.de
bernd-komischke.de
xrheingauerx.de
hotel-nuhnetal.de
hotel-knippschild.de
hotel-nieder.de
dig-id.de bewertung
Euro3,857
Zuletzt aktualisiert: 2022-09-28 00:38:13

dig-id.de hat Semrush globalen Rang von 7,950,841. dig-id.de hat einen geschätzten Wert von € 3,857, basierend auf seinen geschätzten Werbeeinnahmen. dig-id.de empfängt jeden Tag ungefähr 551 einzelne Besucher. Sein Webserver befindet sich in Germany mit der IP-Adresse 185.26.156.210. Laut SiteAdvisor ist dig-id.de sicher zu besuchen.

Verkehr & Wertschätzungen
Kauf-/Verkaufswert Euro€3,857
Tägliche Werbeeinnahmen Euro€99,731
Monatlicher Anzeigenumsatz Euro€33,611
Jährliche Werbeeinnahmen Euro€2,755
Tägliche eindeutige Besucher 551
Hinweis: Alle Traffic- und Einnahmenwerte sind Schätzungen.
DNS Records
Host Type TTL Data
dig-id.de. A 22313 IP: 185.26.156.210
dig-id.de. AAAA 86399 IPV6: 2a00:d0c0:200:0:4ce3:8fff:fec4:d61f
dig-id.de. NS 86400 NS Record: ns16.domserver.de.
dig-id.de. NS 86400 NS Record: ns15.domserver.de.
dig-id.de. NS 86400 NS Record: ns17.domserver.de.
dig-id.de. NS 86400 NS Record: ns18.domserver.de.
dig-id.de. MX 86400 MX Record: 10 hyrrokkin.uberspace.de.
HtmlToTextCheckTime:2022-09-28 00:38:13
Leif’s digital identity Loosely coupled computer gibberish Using SNTP time on Amiga May 23rd, 2021 I never really cared too much about having correct time information available in my Amiga. Maybe not least to the fact that the battery backed-up real-time clocks on Amigas are usually not backed-up by a battery. Getting started Today, I got triggered to change that. Bubbob42 , one of the AmigaOS 3.2 developers, mentioned that he relies on the sntp-client wrapped up in http://aminet.net/package/util/misc/UHCTools. That would certainly be good enough for me. After installing and reading the docs of the package and reading up on NTP (e.g. at https://www.pool.ntp.org/ ) again I discovered that “sntp server de.pool.ntp.org” would get me a correct date, but NOT my local time in Germany. I would just be behind by a few hours. Bummer! Homing in After scratching my head for a bit I checked up on the docs for the Amiga sntp-tool bundled up in UHCTools at http://aminet.net/package/comm/net/sntp .
HTTP Headers
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Sun, 16 Jan 2022 09:46:51 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Location: https://dig-id.de/

HTTP/2 301 
date: Sun, 16 Jan 2022 09:46:51 GMT
content-type: text/html; charset=UTF-8
server: nginx
x-redirect-by: WordPress
location: https://www.dig-id.de/
x-xss-protection: 1; mode=block
x-frame-options: SAMEORIGIN
strict-transport-security: max-age=31536000
x-content-type-options: nosniff
referrer-policy: strict-origin-when-cross-origin

HTTP/2 200 
date: Sun, 16 Jan 2022 09:46:51 GMT
content-type: text/html; charset=UTF-8
vary: Accept-Encoding
server: nginx
link: ; rel="https://api.w.org/"
x-xss-protection: 1; mode=block
x-frame-options: SAMEORIGIN
strict-transport-security: max-age=31536000
x-content-type-options: nosniff
referrer-policy: strict-origin-when-cross-origin