Check DNS, Urls + Redirects, Certificates and Content of your Website



H

Http as Destination - no encryption

Checked:
26.02.2020 00:16:26


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
inwtx.net
A
95.85.40.163
Amsterdam/North Holland/Netherlands (NL) - DigitalOcean, LLC
Hostname: inwtx.net
yes
2
0

AAAA

yes


www.inwtx.net
CNAME
inwtx.net
yes
1
0

A
95.85.40.163
Amsterdam/North Holland/Netherlands (NL) - DigitalOcean, LLC
Hostname: inwtx.net
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 33853, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 12.03.2020, 00:00:00 +, Signature-Inception: 20.02.2020, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: net
net
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 09.03.2020, 17:00:00 +, Signature-Inception: 25.02.2020, 16:00:00 +, KeyTag 33853, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 33853 used to validate the DS RRSet in the parent zone



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 24512, Flags 256



Public Key with Algorithm 8, KeyTag 35886, Flags 257 (SEP = Secure Entry Point)



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 10.03.2020, 17:28:30 +, Signature-Inception: 24.02.2020, 17:23:30 +, KeyTag 35886, Signer-Name: net



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 35886 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 35886, DigestType 2 and Digest "eGKyf19Rbr4ZaARE1M5edimBkxhCxGXwAjZAHYvZc+4=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: inwtx.net
inwtx.net
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "8qpjn4k9k1keptoga26iusmd5up312nn" between the hashed NSEC3-owner "8qpiq0setp7626lnnqqc10sunkmtj0nd" and the hashed NextOwner "8qpp519b5dee9cmpcuafnt0eav0kpmsl". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 8qpiq0setp7626lnnqqc10sunkmtj0nd.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 02.03.2020, 07:33:51 +, Signature-Inception: 24.02.2020, 06:23:51 +, KeyTag 24512, Signer-Name: net



0 DNSKEY RR found




Zone: www.inwtx.net
www.inwtx.net
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
inwtx.net
  ns1.digitalocean.com / 67m10
173.245.58.51
Chicago/Illinois/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::adf5:3a33
Columbus/North Carolina/United States (US) - CLOUDFLARE


  ns2.digitalocean.com / 67m17
173.245.59.41
Chicago/Illinois/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::adf5:3b29
Columbus/North Carolina/United States (US) - CLOUDFLARE


  ns3.digitalocean.com / 67m26
198.41.222.173
Chicago/Illinois/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::c629:dead
Columbus/North Carolina/United States (US) - CLOUDFLARE

net
  a.gtld-servers.net


  b.gtld-servers.net


  c.gtld-servers.net


  d.gtld-servers.net


  e.gtld-servers.net


  f.gtld-servers.net


  g.gtld-servers.net


  h.gtld-servers.net


  i.gtld-servers.net


  j.gtld-servers.net


  k.gtld-servers.net


  l.gtld-servers.net


  m.gtld-servers.net


4. SOA-Entries


Domain:net
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1582672561
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:7


Domain:net
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1582672576
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:inwtx.net
Zone-Name:
Primary:ns1.digitalocean.com
Mail:hostmaster.inwtx.net
Serial:1547640243
Refresh:10800
Retry:3600
Expire:604800
TTL:1800
num Entries:6


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://inwtx.net/
95.85.40.163
301
https://inwtx.net/
Html is minified: 108.24 %
0.053
A
Server: nginx/1.6.2
Date: Tue, 25 Feb 2020 23:16:55 GMT
Content-Type: text/html
Content-Length: 184
Connection: close
Location: https://inwtx.net/

• http://www.inwtx.net/
95.85.40.163
301
https://www.inwtx.net/
Html is minified: 108.24 %
0.050
A
Server: nginx/1.6.2
Date: Tue, 25 Feb 2020 23:16:55 GMT
Content-Type: text/html
Content-Length: 184
Connection: close
Location: https://www.inwtx.net/

• https://inwtx.net/
95.85.40.163
-1

27.543
U
Interner Fehler: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat 95.85.40.163:443

• https://www.inwtx.net/
95.85.40.163
-1

60.147
U
Interner Fehler: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat 95.85.40.163:443

• http://inwtx.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
95.85.40.163
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
301
https://inwtx.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 108.24 %
9.053
A
Visible Content: 301 Moved Permanently nginx/1.6.2
Server: nginx/1.6.2
Date: Tue, 25 Feb 2020 23:18:32 GMT
Content-Type: text/html
Content-Length: 184
Connection: close
Location: https://inwtx.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://www.inwtx.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
95.85.40.163
-14

10.030
T
Timeout - The operation has timed out
Visible Content:

• https://inwtx.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

-14

10.040
T
Timeout - The operation has timed out
Visible Content:

7. Comments


1. General Results, most used to calculate the result

Aname "inwtx.net" is domain, public suffix is "net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
ADomain name could not found. Mistype?
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
CError - no version with Http-Status 200
Hfatal error: No https - result with http-status 200, no encryption

2. DNS- and NameServer - Checks

AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns1.digitalocean.com,ns2.digitalocean.com,ns3.digitalocean.com
AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

3. Content- and Performance-critical Checks

http://www.inwtx.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 95.85.40.163
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
https://inwtx.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 171567 milliseconds, 171.567 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
0
9
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1382432475
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-23 19:03:24
2020-04-22 19:03:24
inwtx.net, mail.inwtx.net, www.inwtx.net - 3 entries


1382372479
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-23 18:23:56
2020-04-22 18:23:56
inwtx.net, mail.inwtx.net, www.inwtx.net - 3 entries


1330454535
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-12-28 11:41:12
2020-03-27 11:41:12
inwtx.net, mail.inwtx.net, www.inwtx.net - 3 entries


1293583716
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-12-08 14:11:47
2020-03-07 14:11:47
inwtx.net, mail.inwtx.net, www.inwtx.net - 3 entries


1238409935
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-11 14:25:04
2020-02-09 14:25:04
inwtx.net, mail.inwtx.net, www.inwtx.net - 3 entries


1157373454
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-09-29 12:24:12
2019-12-28 12:24:12
inwtx.net, www.inwtx.net - 2 entries


1089208001
precert
Leaf-1089208001
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-08-23 22:25:39
2019-11-21 22:25:39
inwtx.net, mail.inwtx.net, www.inwtx.net - 3 entries


1088707812
precert
Leaf-1088707812
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-08-23 15:13:24
2019-11-21 15:13:24
inwtx.net - 1 entries


1029427250
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-21 12:45:00
2019-10-19 12:45:00
inwtx.net, www.inwtx.net - 2 entries


566287009
leaf cert
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
2018-10-02 00:00:00
2019-10-02 12:00:00
*.inwtx.net, inwtx.net, sni.cloudflaressl.com - 3 entries



2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 are listed

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
0
5

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2374222933
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-23 18:03:24
2020-04-22 17:03:24
inwtx.net, mail.inwtx.net, www.inwtx.net
3 entries


2374122345
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-23 17:23:56
2020-04-22 16:23:56
inwtx.net, mail.inwtx.net, www.inwtx.net
3 entries


2272953921
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-12-28 10:41:12
2020-03-27 10:41:12
inwtx.net, mail.inwtx.net, www.inwtx.net
3 entries


2244514534
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-12-08 13:11:47
2020-03-07 13:11:47
inwtx.net, mail.inwtx.net, www.inwtx.net
3 entries


2098838183
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-11 13:25:04
2020-02-09 13:25:04
inwtx.net, mail.inwtx.net, www.inwtx.net
3 entries



11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.inwtx.net



1
0
inwtx.net
0

no CAA entry found
1
0
net
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
inwtx.net
v=spf1 mx a ip4:95.85.40.163 ~all
ok
1
0
www.inwtx.net
v=spf1 mx a ip4:95.85.40.163 ~all
ok
1
0
_acme-challenge.inwtx.net

Name Error - The domain name does not exist
1
0
_acme-challenge.www.inwtx.net

Name Error - The domain name does not exist
1
0
_acme-challenge.inwtx.net.inwtx.net

Name Error - The domain name does not exist
1
0
_acme-challenge.www.inwtx.net.inwtx.net

Name Error - The domain name does not exist
1
0
_acme-challenge.www.inwtx.net.www.inwtx.net

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=83d9f1b7-32fc-4b8b-9ae8-e4c33f2153ea


Last Result: https://check-your-website.server-daten.de/?q=inwtx.net - 2020-02-26 00:16:26


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=inwtx.net" target="_blank">Check this Site: inwtx.net</a>