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

0 in Queue, 1 of max. 8 Checks (11:23:29)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

A

 

Top config

 

Checked:
28.01.2020 09:29:59

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
id.nexta.io
A
51.105.174.203
Amsterdam/North Holland/Netherlands (NL) - Microsoft Corporation
No Hostname found
yes
1
0

AAAA

yes


www.id.nexta.io

Name Error
yes
1
0

 

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: 11.02.2020, 00:00:00 +, Signature-Inception: 21.01.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: io

io
2 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






RRSIG-Owner io., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 10.02.2020, 05:00:00 +, Signature-Inception: 28.01.2020, 04: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 24399, Flags 256






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






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner io., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.02.2020, 15:17:40 +, Signature-Inception: 25.01.2020, 14:17:40 +, KeyTag 24399, Signer-Name: io






RRSIG-Owner io., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.02.2020, 15:17:40 +, Signature-Inception: 25.01.2020, 14:17:40 +, KeyTag 57355, Signer-Name: io






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






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






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






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



Zone: nexta.io

nexta.io
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 "o2v7l14p3kj87kaod7aa5va0i2an369s" between the hashed NSEC3-owner "o2urfbtup1eatqnhaj923tsbuemc8bhm" and the hashed NextOwner "o2vkap1poh8hi72krh12ua7ooo42mha0". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner o2urfbtup1eatqnhaj923tsbuemc8bhm.io., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 15.02.2020, 15:17:40 +, Signature-Inception: 25.01.2020, 14:17:40 +, KeyTag 24399, Signer-Name: io






0 DNSKEY RR found









Zone: id.nexta.io

id.nexta.io
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: www.id.nexta.io

www.id.nexta.io
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.id.nexta.io
•  ns.dandomain.dk

id.nexta.io
•  ns.dandomain.dk
185.25.141.3
Skanderborg/Central Jutland/Denmark (DK) - Zitcom A/S		•
nexta.io
•  ns.dandomain.dk
•

•  ns2.dandomain.dk
•
io
•  a0.nic.io
•

•  a2.nic.io
•

•  b0.nic.io
•

•  c0.nic.io
•

 

4. SOA-Entries


Domain:io
Zone-Name:
Primary:a0.nic.io
Mail:noc.afilias-nst.info
Serial:1497769838
Refresh:10800
Retry:3600
Expire:2764800
TTL:900
num Entries:4


Domain:nexta.io
Zone-Name:
Primary:ns.dandomain.dk
Mail:hostmaster.dandomain.dk
Serial:2020012400
Refresh:14400
Retry:3600
Expire:1209600
TTL:300
num Entries:2


Domain:id.nexta.io
Zone-Name:
Primary:ns.dandomain.dk
Mail:hostmaster.dandomain.dk
Serial:2020012400
Refresh:14400
Retry:3600
Expire:1209600
TTL:300
num Entries:1


Domain:www.id.nexta.io
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

Startaddress: https://id.nexta.io, address used: https://id.nexta.io/, Screenshot created 2020-01-28 09:30:40 +00:0

 

Mobil (412px x 732px)

 

369 milliseconds

 

Screenshot mobile - https://id.nexta.io/
Mobil + Landscape (732px x 412px)

 

385 milliseconds

 

Screenshot mobile landscape - https://id.nexta.io/
Screen (1280px x 1680px)

 

546 milliseconds

 

Screenshot Desktop - https://id.nexta.io/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport412732
content Size412732

 

Good: No horizontal scrollbar. Content-size width = visual Viewport width.

 

Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.2, ECDHE_RSA with X25519, and AES_128_GCM.

 

Chrome-Resources : secure. all served securely. All resources on this page are served securely.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://id.nexta.io/
51.105.174.203
308
https://id.nexta.io/
Html is minified: 108.92 %
0.063
A
Server: nginx/1.17.7
Date: Tue, 28 Jan 2020 08:30:12 GMT
Content-Type: text/html
Content-Length: 171
Connection: close
Location: https://id.nexta.io/

• https://id.nexta.io/
51.105.174.203
200

Html is minified: 122.98 %
3.513
A
small visible content (num chars: 68)
ID.Nexta Login Welcome © 2020 - NextAdvertising.IdentityService
Server: nginx/1.17.7
Date: Tue, 28 Jan 2020 08:30:12 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Strict-Transport-Security: max-age=15724800; includeSubDomains
Content-Encoding: gzip

• http://id.nexta.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
51.105.174.203
308
https://id.nexta.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 108.92 %
0.064
A
Visible Content: 308 Permanent Redirect nginx/1.17.7
Server: nginx/1.17.7
Date: Tue, 28 Jan 2020 08:30:16 GMT
Content-Type: text/html
Content-Length: 171
Connection: close
Location: https://id.nexta.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• https://id.nexta.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

404


3.296
A
Not Found
Visible Content:
Server: nginx/1.17.7
Date: Tue, 28 Jan 2020 08:30:17 GMT
Content-Length: 0
Connection: close
Strict-Transport-Security: max-age=15724800; includeSubDomains

 

7. Comments


1. General Results, most used to calculate the result

Aname "id.nexta.io" is subdomain, public suffix is "io", top-level-domain-type is "country-code", Country is British Indian Ocean Territory (the), tld-manager is "IO Top Level Domain Registry"
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: every https has a Strict Transport Security Header
AGood: HSTS has includeSubdomains - directive
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Ahttp://id.nexta.io/ 51.105.174.203
308
https://id.nexta.io/
Correct redirect http - https with the same domain name
BWarning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15724800 seconds = 182 days found

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)


3. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
AGood: All SOA have the same Serial Number
AGood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create wildcard-certificates

4. Content- and Performance-critical Checks

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
https://id.nexta.io/ 51.105.174.203
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
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
https://id.nexta.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
3.296 seconds
Warning: 404 needs more then one second
ADuration: 46067 milliseconds, 46.067 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
id.nexta.io
51.105.174.203
443
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
id.nexta.io
51.105.174.203
443
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
 Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=id.nexta.io


2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


id.nexta.io
id.nexta.io
443
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok

id.nexta.io
id.nexta.io
443
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
 Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=id.nexta.io


2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

 

9. Certificates

1.
1.
CN=id.nexta.io
23.01.2020
22.04.2020
1689 days expired		id.nexta.io - 1 entry
1.
1.
CN=id.nexta.io
23.01.2020

22.04.2020
1689 days expired


id.nexta.io - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:038D20944AB5298976987BF8F0C428351FAA
Thumbprint:B1E99D733BE19CE3BC07F8FAEA652E020E83CB89
SHA256 / Certificate:zwTgSVoo2/PV8JBRaF1CisTSmdCzKD2i6Shm8SPlzYY=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):434143f877d19f11dd154e31d2a502ec6e656492559250e4da14126e2b076646
SHA256 hex / Subject Public Key Information (SPKI):434143f877d19f11dd154e31d2a502ec6e656492559250e4da14126e2b076646
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
1360 days expired

2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
1360 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
1163 days expired

3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
1163 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




 

10. Last Certificates - Certificate Transparency Log Check

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

Small Code Update - wait one minute

 

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

Small Code Update - wait one minute

 

11. Html-Content - Entries

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

 

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

  Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

Small Code update, wait one minute

 

13. 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.

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
id.nexta.io
0

no CAA entry found
1
0
nexta.io
9
issuewild
letsencrypt.org
1
0
io
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
nexta.io
MS=ms11659206
ok
1
0
nexta.io
MS=ms89916888
ok
1
0
nexta.io
v=spf1 a include:spf.protection.outlook.com ip4:194.150.113.0/24 ip4:194.150.112.0/24 include:spf.mandrillapp.com -all
ok
1
0
id.nexta.io

ok
1
0
_acme-challenge.id.nexta.io

Name Error - The domain name does not exist
1
0
_acme-challenge.id.nexta.io.nexta.io

Name Error - The domain name does not exist
1
0
_acme-challenge.id.nexta.io.id.nexta.io

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

 

 

Permalink: https://check-your-website.server-daten.de/?i=bc50bb6a-fe64-440e-863a-1ff6e8ef5cca

 

Last Result: https://check-your-website.server-daten.de/?q=id.nexta.io - 2020-01-28 09:29:59

 

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

 

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

 

 

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=id.nexta.io

 

 

Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • USt-IdNr.: DE221734518

 

Errors, ideas, questions? Use the Contact form • A project using Server-Daten - Web Database solutions