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




Q

http sent over port 443

Checked:
13.07.2019 19:08:10


Older results


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
maxserp.com
A
155.138.210.173
Atlanta/Georgia/United States (US) - Choopa
Hostname: 155.138.210.173.vultr.com
yes
2
0

AAAA

yes


www.maxserp.com
C
maxserp.com
yes
1
0

A
155.138.210.173
Atlanta/Georgia/United States (US) - Choopa
Hostname: 155.138.210.173.vultr.com
yes



2. DNSSEC

Zone (*)DNSSEC - Informations (beta)

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 59944, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.08.2019, 00:00:00, Signature-Inception: 11.07.2019, 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: com
com
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.07.2019, 05:00:00, Signature-Inception: 13.07.2019, 04:00:00, KeyTag 59944, Signer-Name: (root)



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 3800, Flags 256



Public Key with Algorithm 8, KeyTag 17708, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.07.2019, 18:25:33, Signature-Inception: 11.07.2019, 18:20:33, KeyTag 30909, Signer-Name: com



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



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

Zone: maxserp.com
maxserp.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.



0 DNSKEY RR found





Zone: www.maxserp.com
www.maxserp.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
maxserp.com
  ns1.vultr.com / ams1-authdns1.choopadns.com
173.199.96.96
Dallas/Texas/United States (US) - Choopa, LLC


 
2001:19f0:ccd::1
Chicago/Illinois/United States (US) - Choopa, LLC


  ns2.vultr.com / ams1-authdns1.choopadns.com
173.199.96.97
Dallas/Texas/United States (US) - Choopa, LLC


 
2001:19f0:ccd::2
Chicago/Illinois/United States (US) - Choopa, LLC

com
  a.gtld-servers.net


  b.gtld-servers.net


T  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:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1563037676
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:2


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


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


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


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


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


Domain:maxserp.com
Primary:ns1.vultr.com
Mail:dnsadm.choopa.com
Serial:1562786338
Refresh:10800
Retry:3600
Expire:604800
TTL:3600
num Entries:4


5. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://www.maxserp.com/
155.138.210.173
301
http://maxserp.com/
0.257
D
Date: Sat, 13 Jul 2019 17:09:28 GMT
Server: Apache/2.4.38 (Ubuntu)
X-Redirect-By: WordPress
Location: http://maxserp.com/
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• http://maxserp.com/
155.138.210.173
200

0.290
H
Date: Sat, 13 Jul 2019 17:09:28 GMT
Server: Apache/2.4.38 (Ubuntu)
Link: <http://maxserp.com/index.php/wp-json/>; rel="https://api.w.org/"
Vary: Accept-Encoding
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8

• https://maxserp.com/
155.138.210.173
-4

0.477
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. The handshake failed due to an unexpected packet format.

• https://www.maxserp.com/
155.138.210.173
-4

0.480
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. The handshake failed due to an unexpected packet format.

• http://www.maxserp.com:443/
155.138.210.173
301
http://maxserp.com/
0.263
Q
Visible Content:
Date: Sat, 13 Jul 2019 17:09:30 GMT
Server: Apache/2.4.38 (Ubuntu)
X-Redirect-By: WordPress
Location: http://maxserp.com/
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• http://maxserp.com:443/
155.138.210.173
200

0.280
Q
Visible Content:
Date: Sat, 13 Jul 2019 17:09:30 GMT
Server: Apache/2.4.38 (Ubuntu)
Link: <http://maxserp.com/index.php/wp-json/>; rel="https://api.w.org/"
Vary: Accept-Encoding
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8

• http://maxserp.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
155.138.210.173
404

0.244
A
Not Found
Visible Content:
Date: Sat, 13 Jul 2019 17:09:30 GMT
Server: Apache/2.4.38 (Ubuntu)
Content-Length: 344
Connection: close
Content-Type: text/html; charset=iso-8859-1

• http://www.maxserp.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
155.138.210.173
404

0.246
A
Not Found
Visible Content:
Date: Sat, 13 Jul 2019 17:09:30 GMT
Server: Apache/2.4.38 (Ubuntu)
Content-Length: 348
Connection: close
Content-Type: text/html; charset=iso-8859-1

6. Comments (GZip / Html minfied / Cache-Control is beta)

Aname "maxserp.com" is domain, public suffix is "com", 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
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
Dhttp://www.maxserp.com/ 155.138.210.173
301
http://maxserp.com/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Hfatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Qhttp://maxserp.com:443/ 155.138.210.173
200

Misconfiguration: http sent over port 443. Wrong port forwarding port 443 to port 80 or wrong vHost definition. If you use a virtual Host <VirtualHost ip-address:443>, try <VirtualHost *:443>.
Qhttp://www.maxserp.com:443/ 155.138.210.173
301
http://maxserp.com/
Misconfiguration: http sent over port 443. Wrong port forwarding port 443 to port 80 or wrong vHost definition. If you use a virtual Host <VirtualHost ip-address:443>, try <VirtualHost *:443>.
XFatal error: Nameserver doesn't support TCP connection: c.gtld-servers.net: Timeout
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
XNameserver Timeout checking Echo Capitalization: c.gtld-servers.net
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
XNameserver Timeout checking EDNS512: c.gtld-servers.net
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: c.gtld-servers.net: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
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.
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: 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: 85753 milliseconds, 85.753 seconds


7. Connections (http/2- and additional Tls.1.0/1.1/1.2 checks are BETA)

No connection informations found. Perhaps only http - connections.


8. Certificates

No certificate informations found. Perhaps only http - connections.


9. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates

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

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1012244376
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-11 21:21:33
2019-10-09 21:21:33
maxserp.com - 1 entries


1011783327
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-11 15:03:56
2019-10-09 15:03:56
maxserp.com - 1 entries


1011691043
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-11 13:45:05
2019-10-09 13:45:05
maxserp.com - 1 entries


1010264361
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-10 18:24:23
2019-10-08 18:24:23
maxserp.com - 1 entries


1010165214
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-10 16:52:37
2019-10-08 16:52:37
maxserp.com - 1 entries


910074332
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-05-13 20:27:03
2019-08-11 20:27:03
il.maxserp.com, maxserp.com, www.maxserp.com - 3 entries



2. Source crt.sh - old and new certificates, sometimes very slow (currently no newer certificates - read Crt.sh has stopped - Letsencrypt-forum - may work next week again - 2019-12-02 - but I must check the code).

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

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1661588658
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-11 19:21:33
2019-10-09 19:21:33
maxserp.com
1 entries


1660791906
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-11 13:03:56
2019-10-09 13:03:56
maxserp.com
1 entries


1660482479
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-11 11:45:05
2019-10-09 11:45:05
maxserp.com
1 entries


1664525575
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-10 16:24:23
2019-10-08 16:24:23
maxserp.com
1 entries


1657215629
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-10 14:52:37
2019-10-08 14:52:37
maxserp.com
1 entries


1482083853
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-05-13 18:27:03
2019-08-11 18:27:03
il.maxserp.com, maxserp.com, www.maxserp.com
3 entries


1288696126
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-03-13 20:21:24
2019-06-11 19:21:24
il.maxserp.com, maxserp.com, www.maxserp.com
3 entries


1102306265
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-01-11 20:22:35
2019-04-11 19:22:35
il.maxserp.com, maxserp.com, www.maxserp.com
3 entries


941611091
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-11-12 20:18:14
2019-02-10 20:18:14
il.maxserp.com, maxserp.com, www.maxserp.com
3 entries


791348074
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-09-13 18:15:59
2018-12-12 19:15:59
il.maxserp.com, maxserp.com, www.maxserp.com
3 entries


618624791
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-07-15 09:31:54
2018-10-13 09:31:54
il.maxserp.com, maxserp.com, www.maxserp.com
3 entries



10. Html-Content - Entries

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


11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.maxserp.com



1
0
maxserp.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
maxserp.com

ok
1
0
www.maxserp.com


1
0
_acme-challenge.maxserp.com


1
0
_acme-challenge.www.maxserp.com


1
0
_acme-challenge.maxserp.com.maxserp.com


1
0
_acme-challenge.www.maxserp.com.maxserp.com


1
0
_acme-challenge.www.maxserp.com.www.maxserp.com


1
0


13. Portchecks (BETA)

Domain or IPPortDescriptionResultAnswer
maxserp.com
21




maxserp.com
21




maxserp.com
22

open
SSH-2.0-OpenSSH_7.9p1 Ubuntu-10

maxserp.com
22

open
SSH-2.0-OpenSSH_7.9p1 Ubuntu-10

maxserp.com
25




maxserp.com
25




maxserp.com
53




maxserp.com
53




maxserp.com
110




maxserp.com
110




maxserp.com
143




maxserp.com
143




maxserp.com
465




maxserp.com
465




maxserp.com
587




maxserp.com
587




maxserp.com
993




maxserp.com
993




maxserp.com
995




maxserp.com
995




maxserp.com
1433




maxserp.com
1433




maxserp.com
2082




maxserp.com
2082




maxserp.com
2083




maxserp.com
2083




maxserp.com
2086




maxserp.com
2086




maxserp.com
2087




maxserp.com
2087




maxserp.com
2089




maxserp.com
2089




maxserp.com
3306




maxserp.com
3306




maxserp.com
5224




maxserp.com
5224




maxserp.com
5432




maxserp.com
5432




maxserp.com
8443




maxserp.com
8443




maxserp.com
8447




maxserp.com
8447




maxserp.com
8880




maxserp.com
8880




www.maxserp.com
21




www.maxserp.com
21




www.maxserp.com
22

open
SSH-2.0-OpenSSH_7.9p1 Ubuntu-10

www.maxserp.com
22

open
SSH-2.0-OpenSSH_7.9p1 Ubuntu-10

www.maxserp.com
25




www.maxserp.com
25




www.maxserp.com
53




www.maxserp.com
53




www.maxserp.com
110




www.maxserp.com
110




www.maxserp.com
143




www.maxserp.com
143




www.maxserp.com
465




www.maxserp.com
465




www.maxserp.com
587




www.maxserp.com
587




www.maxserp.com
993




www.maxserp.com
993




www.maxserp.com
995




www.maxserp.com
995




www.maxserp.com
1433




www.maxserp.com
1433




www.maxserp.com
2082




www.maxserp.com
2082




www.maxserp.com
2083




www.maxserp.com
2083




www.maxserp.com
2086




www.maxserp.com
2086




www.maxserp.com
2087




www.maxserp.com
2087




www.maxserp.com
2089




www.maxserp.com
2089




www.maxserp.com
3306




www.maxserp.com
3306




www.maxserp.com
5224




www.maxserp.com
5224




www.maxserp.com
5432




www.maxserp.com
5432




www.maxserp.com
8443




www.maxserp.com
8443




www.maxserp.com
8447




www.maxserp.com
8447




www.maxserp.com
8880




www.maxserp.com
8880




155.138.210.173
21




155.138.210.173
21




155.138.210.173
22

open
SSH-2.0-OpenSSH_7.9p1 Ubuntu-10

155.138.210.173
22

open
SSH-2.0-OpenSSH_7.9p1 Ubuntu-10

155.138.210.173
25




155.138.210.173
25




155.138.210.173
53




155.138.210.173
53




155.138.210.173
110




155.138.210.173
110




155.138.210.173
143




155.138.210.173
143




155.138.210.173
465




155.138.210.173
465




155.138.210.173
587




155.138.210.173
587




155.138.210.173
993




155.138.210.173
993




155.138.210.173
995




155.138.210.173
995




155.138.210.173
1433




155.138.210.173
1433




155.138.210.173
2082




155.138.210.173
2082




155.138.210.173
2083




155.138.210.173
2083




155.138.210.173
2086




155.138.210.173
2086




155.138.210.173
2087




155.138.210.173
2087




155.138.210.173
2089




155.138.210.173
2089




155.138.210.173
3306




155.138.210.173
3306




155.138.210.173
5224




155.138.210.173
5224




155.138.210.173
5432




155.138.210.173
5432




155.138.210.173
8443




155.138.210.173
8443




155.138.210.173
8447




155.138.210.173
8447




155.138.210.173
8880




155.138.210.173
8880






Permalink: https://check-your-website.server-daten.de/?i=0319396c-582e-423d-8457-4441fb2a9c0f


Last Result: https://check-your-website.server-daten.de/?q=maxserp.com - 2019-07-13 19:08:10


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

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